Red Hat Bugzilla – Bug 1222707
ISO repos are not published via http
Last modified: 2017-09-14 06:26:44 EDT
Description of problem: I have multiple ISO repos (rhel workstation and server) that are synced but are only being published via https. There is no option in the UI to change the publish option to allow http.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created redmine issue http://projects.theforeman.org/issues/10958 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/10958 has been closed ------------- Christine Fouant Applied in changeset commit:katello|b0f032d4e09ffc6156ff9023489ec2fa9c284b20.
Failed. I synced an iso repo. While looking at the repo, it showed the following: Published At: http://$host/pulp/isos/RbeQr-Red_Hat_Satellite_Capsule-Red_Hat_Satellite_Capsule_6_1_for_RHEL_7_Server_ISOs_x86_64 When I clicked on the url, the browser failed with the following error: Secure Connection Failed An error occurred during a connection to ibm-x3250m4-05.lab.eng.rdu2.redhat.com. SSL peer was unable to negotiate an acceptable set of security parameters. (Error code: ssl_error_handshake_failure_alert) The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem. Note: 1. I already imported the katello-server-ca.crt from the satellite host to my browser 2. Screenshots attached
Upstream bug component is Content Management
Merging of https://github.com/Katello/puppet-katello/pull/75 should fix the failure.
Failed again in Satellite 6.1.4 Compose 2 build following the same steps mentioned in Comment 7.
Ignore Comment 14, the isos were not really synced earlier. I tried resyncing and it works fine now. I retried the same steps as mentioned in Comment 7 and now I am able to browse through the isos and download them successfully.
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/RHBA-2015:2474