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.
DescriptionJaskaran Singh Narula
2021-07-19 18:17:34 UTC
Description of problem:
Unable to view content on Satellite under http://satellite.example.com/pulp/content/
Version-Release number of selected component (if applicable):
satellite-installer-6.10.0.3-1.el7sat.noarch
satellite-common-6.10.0-0.4.beta.el7sat.noarch
satellite-cli-6.10.0-0.4.beta.el7sat.noarch
satellite-maintain-0.0.1-1.el7sat.noarch
satellite-6.10.0-0.4.beta.el7sat.noarch
How reproducible:
100%
Steps to Reproduce:
1. build a fresh satellite 6.10 Beta.
2. Enable and sync any Red Hat repositories.
3. Enter the URL -->> http://satellite.example.com/pulp/content/
Actual results:
Pages load with error:
--------------------------
500 Internal Server Error
Server got itself in trouble
------------------------------
Expected results:
Expected to see the pulp content (like packages and errata) after the migration to pulp3.
Additional info:
Comment 2Tanya Tereshchenko
2021-07-23 16:54:48 UTC
This should be fixed in a snap which has pulpcore 3.14.
Please check your pulpcore version.
If it's below 3.14, try the fresh 6.10 snap.
If it's 3.14, let us know, we would need to investigate.
Comment 3pulp-infra@redhat.com
2021-07-23 17:16:37 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 4pulp-infra@redhat.com
2021-07-23 17:16:38 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 5pulp-infra@redhat.com
2021-07-23 18:09:31 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Steps to test
1. build a fresh satellite 6.10 Beta.
2. Enable and sync any Red Hat repositories.
3. Enter the URL -->> http://satellite.example.com/pulp/content/
Expected result:
Should see list of synced repos
Actual:
List of synced repos show up.
Verified on 6.10 snap 11 with python3-pulp-rpm-3.14.0-1.el7pc.noarch
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 (Moderate: Satellite 6.10 Release), 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/RHSA-2021:4702