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.
Customer tries to publish Content view after 6.10 migration, receives this error on one or more subtasks:
~~~
1) Task identifier: 2b1f9707-77bd-4379-a029-ddb574a75790
Task action: Publish
Task errors: Error message: the server returns an error
HTTP status code: 404
Response headers: {"Date"=>"Mon, 31 Jan 2022 17:45:19 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"23", "Correlation-ID"=>"75b31093-271d-4224-a03d-9666c209e990", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 satellite.example.com"}
Response body: {"detail":"Not found."}
~~~
These are from api calls to Pulp, seen here:
~~~
sos_commands/logs/journalctl_--no-pager:Jan 31 13:00:49 satellite.example.com pulpcore-api[76007]: pulp [b6d31759-764d-4894-ad93-0df271982f81]: django.request:WARNING: Not Found: /pulp/api/v3/repositories/rpm/rpm/7fc6603f-3a73-42a9-98d2-a72679181db9/
sos_commands/logs/journalctl_--no-pager:Jan 30 23:53:28 satellite.example.com pulpcore-api[78718]: pulp [5afbd3c0-c5d2-4209-975b-1e94eb0346cc]: django.request:WARNING: Not Found: /pulp/api/v3/repositories/rpm/rpm/4d99fcef-e958-49bb-817e-3e74c0ae3c0c/
~~~
The repo is in foremandb but not in pulpcore. To try to address this the correct_repositories rake was used. In one case this found 289 repos to clean:
~~~
▲ ~/cases/case rg 'Missing|Deleting' rakeoutput.txt | tail -n4
Repository 2316 Missing
Deleting 2316
Repository 2319 Missing
Deleting 2319
▲ ~/cases/case rg Deleting rakeoutput.txt | wc
289 578 4268
~~~
After properly cleaning the previous publish attempts, the CV is published again but receives the same error on the subtasks. To resolve the issue this rake was needed:
~~~
foreman-rake console << EORAKE
Katello::Pulp3::RepositoryReference.all.select do |ref|
api = Katello::RepositoryTypeManager.repository_types[ref.root_repository.content_type].pulp3_api_class.new(SmartProxy.pulp_primary)
api.repositories_api.read(ref.repository_href)
rescue => e
if e&.code == 404
ref.destroy
end
end
EORAKE
~~~
After this rake the CV published without error. Creating this BZ to double-check if the correct_repos rake needs adjustment to properly handle occasions where the above rake solves the problem of repos existing in foreman but not in pulpcore.
Customer tries to publish Content view after 6.10 migration, receives this error on one or more subtasks: ~~~ 1) Task identifier: 2b1f9707-77bd-4379-a029-ddb574a75790 Task action: Publish Task errors: Error message: the server returns an error HTTP status code: 404 Response headers: {"Date"=>"Mon, 31 Jan 2022 17:45:19 GMT", "Server"=>"gunicorn", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, PUT, PATCH, DELETE, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"23", "Correlation-ID"=>"75b31093-271d-4224-a03d-9666c209e990", "Access-Control-Expose-Headers"=>"Correlation-ID", "Via"=>"1.1 satellite.example.com"} Response body: {"detail":"Not found."} ~~~ These are from api calls to Pulp, seen here: ~~~ sos_commands/logs/journalctl_--no-pager:Jan 31 13:00:49 satellite.example.com pulpcore-api[76007]: pulp [b6d31759-764d-4894-ad93-0df271982f81]: django.request:WARNING: Not Found: /pulp/api/v3/repositories/rpm/rpm/7fc6603f-3a73-42a9-98d2-a72679181db9/ sos_commands/logs/journalctl_--no-pager:Jan 30 23:53:28 satellite.example.com pulpcore-api[78718]: pulp [5afbd3c0-c5d2-4209-975b-1e94eb0346cc]: django.request:WARNING: Not Found: /pulp/api/v3/repositories/rpm/rpm/4d99fcef-e958-49bb-817e-3e74c0ae3c0c/ ~~~ The repo is in foremandb but not in pulpcore. To try to address this the correct_repositories rake was used. In one case this found 289 repos to clean: ~~~ ▲ ~/cases/case rg 'Missing|Deleting' rakeoutput.txt | tail -n4 Repository 2316 Missing Deleting 2316 Repository 2319 Missing Deleting 2319 ▲ ~/cases/case rg Deleting rakeoutput.txt | wc 289 578 4268 ~~~ After properly cleaning the previous publish attempts, the CV is published again but receives the same error on the subtasks. To resolve the issue this rake was needed: ~~~ foreman-rake console << EORAKE Katello::Pulp3::RepositoryReference.all.select do |ref| api = Katello::RepositoryTypeManager.repository_types[ref.root_repository.content_type].pulp3_api_class.new(SmartProxy.pulp_primary) api.repositories_api.read(ref.repository_href) rescue => e if e&.code == 404 ref.destroy end end EORAKE ~~~ After this rake the CV published without error. Creating this BZ to double-check if the correct_repos rake needs adjustment to properly handle occasions where the above rake solves the problem of repos existing in foreman but not in pulpcore.