Version Katello nightly Pulpcore 3.18.5 pulp-rpm 3.17.5 Describe the bug I created an alternate content source with the following RH CDN path: https://cdn.redhat.com/content/dist/layered/rhel8/x86_64/advanced-virt/os At refresh time, I saw the following error: { "pulp_href": "/pulp/api/v3/tasks/fa96f3a4-1b2b-4530-a0b4-b6adf4fdc3e5/", "pulp_created": "2022-07-25T21:03:44.164063Z", "state": "failed", "name": "pulp_rpm.app.tasks.synchronizing.synchronize", "logging_cid": "660e71d7-6c15-4dda-a381-b2f9f19ca743", "started_at": "2022-07-25T21:03:44.196268Z", "finished_at": "2022-07-25T21:03:44.441820Z", "error": { "traceback": " File \"/usr/local/lib/python3.9/site-packages/pulpcore/tasking/pulpcore_worker.py\", line 410, in _perform_task\n result = func(*args, **kwargs)\n File \"/usr/lib/python3.9/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 464, in synchronize\n remote_url = fetch_remote_url(remote, url)\n File \"/usr/lib/python3.9/site-packages/pulp_rpm/app/tasks/synchronizing.py\", line 292, in fetch_remote_url\n raise ValueError(\n", "description": "Remote URL https://cdn.redhat.com/content/dist/layered/rhel8/x86_64/advanced-virt/os for Alternate Content Source is invalid" }, "worker": "/pulp/api/v3/workers/1591cc69-60de-4f06-b566-5ff37311759f/", "parent_task": null, "child_tasks": [], "task_group": "/pulp/api/v3/task-groups/ba681a0b-44fc-4390-bbe7-a13434ad2a18/", "progress_reports": [], "created_resources": [], "reserved_resources_record": [ "shared:/pulp/api/v3/acs/rpm/rpm/e69b2e9f-22f6-4310-9265-64fcb8bc586b/", "shared:/pulp/api/v3/remotes/rpm/rpm/43c602fd-305d-4765-8695-42c792ec0b84/" ] } To Reproduce Steps to reproduce the behavior: Create an ACS with the appropriate remote configuration to sync the repository above. Refresh the ACS Expected behavior The ACS refreshes without error. Additional context Remote options: {:tls_validation=>true, :name=>"Advanced_Virtualization_for_RHEL_8_x86_64_RPMs-12300", :url=>"https://cdn.redhat.com/content/dist/layered/rhel8/x86_64/advanced-virt/os", :proxy_url=>nil, :proxy_username=>nil, :proxy_password=>nil, :total_timeout=>3600, :connect_timeout=>60, :sock_connect_timeout=>60, :sock_read_timeout=>3600, :rate_limit=>0, :username=>nil, :password=>nil, :client_cert=> 'redacted', :client_key=>'redacted', :ca_cert=>'redacted', :policy=>"on_demand" }
This BZ is to track a nightly issue only -- this is not yet in Satellite.
The Pulp upstream bug status is at closed. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
The fix (which is just a better error message) is actually in 6.11 and 6.12 currently, but you wouldn't be able to tell because as Ian mentioned ACS isn't supported until 6.13
Whoops, didn't mean to close. It can still be verified for 6.13
I guess I can just mark it modified since whenever the first snap happens, it will already be there.
Verified in 6.13.0 snap 10 (python39-pulp-rpm-3.18.9-1.el8pc.noarch) - Error message was improved: "description"=>"ACS remote for url 'https://cdn.redhat.com/content/dist/layered/rhel8/x86_64/advanced-virt/os/' raised an error '403: Forbidden'. Please check your ACS remote configuration."
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 (Important: Satellite 6.13 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-2023:2097