Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Synchronizing repositories that are published via HTTP and HTTPS should always default to the more secure method available.
After publishing a Content View with a repository that has both HTTP and HTTPS enabled, the capsule will attempt to synchronize over HTTP rather than HTTPS. Because HTTP is blocked between the Parent and the Capsule, the repository will not sync.
Version-Release number of selected component (if applicable):
Sat:
satellite-6.2.0-8.2.beta.el7sat.noarch
pulp-server-2.8.1.3-1.el7sat.noarch
tfm-rubygem-foreman-tasks-0.7.16-1.fm1_11.el7.noarch
Capsule:
satellite-capsule-6.2.0-8.2.beta.el7sat.noarch
How reproducible:
Everytime
Steps to Reproduce:
1 Sync RHEL7 Kickstart , RHEL 7 7Server and a custom channel
2. Assign Library to your capsule
# hammer -u <user> -p <pass> capsule content add-lifecycle-environment \
--organization-id 1 --id 4 --environment-id 1
3. Make the capsule to sync the content
# hammer -u <user> -p <pass> capsule content synchronize --id 4
Actual results:
Any repository that has HTTPS enabled will synchronize fine. Any repository that has both HTTP and HTTPS enabled will fail as pulp attempts to use HTTP (least secure)
May 01 09:36:40 <capsule name> pulp[6243]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (3): <parent name>
May 01 09:36:40 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=3, connect=3, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x452e9d0>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64/content/dist/rhel/server/7/7.2/x86_64/kickstart
May 01 09:36:40 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (3): <parent name>
May 01 09:36:50 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=2, connect=2, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x452e750>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64/content/dist/rhel/server/7/7.2/x86_64/kickstart
May 01 09:36:50 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (4): <parent name>
May 01 09:36:50 <capsule name> pulp[6243]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=2, connect=2, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x4fd2810>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64-cv/content/dist/rhel/server/7/7.2/x86_64/kickstart
Expected results:
All repositories that have 'Publish via HTTPS' and 'Publish via HTTP' should default to HTTPS.
Additional info:
verified on snap 19.1
how I tested:
* set up sat + capsule
* create a repo that is published on https and http, add to CV, publish CV
* on sat, tail -f /var/log/httpd/* | grep <capsule ip>
* sync capsule
result:
all GET calls for content are over ssl, and no errors in /var/log/messages on capsule
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-2016:1501
Description of problem: Synchronizing repositories that are published via HTTP and HTTPS should always default to the more secure method available. After publishing a Content View with a repository that has both HTTP and HTTPS enabled, the capsule will attempt to synchronize over HTTP rather than HTTPS. Because HTTP is blocked between the Parent and the Capsule, the repository will not sync. Version-Release number of selected component (if applicable): Sat: satellite-6.2.0-8.2.beta.el7sat.noarch pulp-server-2.8.1.3-1.el7sat.noarch tfm-rubygem-foreman-tasks-0.7.16-1.fm1_11.el7.noarch Capsule: satellite-capsule-6.2.0-8.2.beta.el7sat.noarch How reproducible: Everytime Steps to Reproduce: 1 Sync RHEL7 Kickstart , RHEL 7 7Server and a custom channel 2. Assign Library to your capsule # hammer -u <user> -p <pass> capsule content add-lifecycle-environment \ --organization-id 1 --id 4 --environment-id 1 3. Make the capsule to sync the content # hammer -u <user> -p <pass> capsule content synchronize --id 4 Actual results: Any repository that has HTTPS enabled will synchronize fine. Any repository that has both HTTP and HTTPS enabled will fail as pulp attempts to use HTTP (least secure) May 01 09:36:40 <capsule name> pulp[6243]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (3): <parent name> May 01 09:36:40 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=3, connect=3, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x452e9d0>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64/content/dist/rhel/server/7/7.2/x86_64/kickstart May 01 09:36:40 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (3): <parent name> May 01 09:36:50 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=2, connect=2, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x452e750>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64/content/dist/rhel/server/7/7.2/x86_64/kickstart May 01 09:36:50 <capsule name> pulp[6245]: requests.packages.urllib3.connectionpool:INFO: Starting new HTTP connection (4): <parent name> May 01 09:36:50 <capsule name> pulp[6243]: requests.packages.urllib3.connectionpool:WARNING: Retrying (Retry(total=2, connect=2, read=5, redirect=None)) after connection broken by 'ConnectTimeoutError(<requests.packages.urllib3.connection.HTTPConnection object at 0x4fd2810>, 'Connection to <parent name> timed out. (connect timeout=6.05)')': /pulp/repos/Enterprise_Unix_Engineering/LAB/eue-7-server-x86_64-cv/content/dist/rhel/server/7/7.2/x86_64/kickstart Expected results: All repositories that have 'Publish via HTTPS' and 'Publish via HTTP' should default to HTTPS. Additional info: