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:
When trying to sync the atomic host beta ostree repo, I see the following error:
OST0005: Fetch summary failed. Reason: GLib.Error('Server returned HTTP 404', 'g-io-error-quark', 1)

Version-Release number of selected component (if applicable):
Satellite 6.5.0 Snap 20
This is likely a regression from Snap 19.

How reproducible:
Always

Steps to Reproduce:
1. Upload a manifest that provides Red Hat Enterprise Linux Atomic Host Beta Trees x86_64
2. Enable Red Hat Enterprise Linux Atomic Host Beta Trees x86_64
3. Synchronize Red Hat Enterprise Linux Atomic Host Beta Trees x86_64

Actual results:
OST0005: Fetch summary failed. Reason: GLib.Error('Server returned HTTP 404', 'g-io-error-quark', 1)

Expected results:
The repository syncs successfully 

Additional info:
This also fails with Red Hat Enterprise Linux Atomic Host Preview Trees x86_64

This seems like a problem with the CDN. I've relayed the information to the appropriate team.

@Djordje - We have never released Atomic Host beta.

Removing regression as this looks to have been caused from the content side. 

Additionally, I'd open up the request that if this is not a fault of the pulp end, then the pulp team present the error in a better way.

Something stating what specifically was not available.

There are currently no plans to add this request to Pulp 2 roadmap.
Pulp 2 is in maintenance mode and accepting critical bugs/requests only.