Description of problem: Classic issue when upgrading from RHUI2 to RHUI3 or when old Content CA expires is that old clients are denied content. To circumvent that we should implement "Legacy CA" feature into OID validator. Version-Release number of selected component (if applicable): RHUI 3 How reproducible: Always Steps to Reproduce: 1. Have client created with old CA (for example RHUI2). 2. Change repo path to point to new RHUI (for example RHUI3). 3. yum repolist Actual results: Two things might happen: 1. You don't have Apache SSL cert signed by same CA as on RHUI2 - in that case, just set sslVerify=0. 2. You will get "Peer does not recognize and trust the CA that issued your certificate." Expected results: Just changing of repo url (rhui address) or redirecting is enough. Additional info:
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2019:1283