FYI, during the latest upgrade test I did not see this issues again, because we are simply not adding the SSL repo in the repo file anymore.
FYI, during the latest upgrade test I did not see this issues again, because we are simply not adding the SSL repo in the repo file anymore.