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.
Created attachment 1456494[details]
Screenshot of the portal error
Description of problem:
Life Cycle contents are not synced to the capsule after successful installation. It is giving "SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca" in the portal when trying to sync the content. After troubleshooting it seems that there is a problem with the pulp certificate. The problem can be solved by running "satellite-installer --scenario capsule --upgrade"
Two different satellite deployments with each have at least 2 capsules and the same behaviour was found.
Version-Release number of selected component (if applicable):
Satellite 6.3.2 with puppet 4 repositories
RHEL7.5 with latest updates
How reproducible:
Steps to Reproduce:
1. Install satellite and configure life cycle environment and content views
2. Install Capsule
3. enable the content to be synced and start the sync
Actual results:
Error in the portal "SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca"
Expected results:
The sync process should start and a progress bar should be shown.
Additional info:
There is a support case "02119905" that was opened which have some more details
Created attachment 1456494 [details] Screenshot of the portal error Description of problem: Life Cycle contents are not synced to the capsule after successful installation. It is giving "SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca" in the portal when trying to sync the content. After troubleshooting it seems that there is a problem with the pulp certificate. The problem can be solved by running "satellite-installer --scenario capsule --upgrade" Two different satellite deployments with each have at least 2 capsules and the same behaviour was found. Version-Release number of selected component (if applicable): Satellite 6.3.2 with puppet 4 repositories RHEL7.5 with latest updates How reproducible: Steps to Reproduce: 1. Install satellite and configure life cycle environment and content views 2. Install Capsule 3. enable the content to be synced and start the sync Actual results: Error in the portal "SSL_connect returned=1 errno=0 state=SSLv3 read server session ticket A: tlsv1 alert unknown ca" Expected results: The sync process should start and a progress bar should be shown. Additional info: There is a support case "02119905" that was opened which have some more details