Description of problem:
Pstree sync of the rhel-atomic-host-beta-ostree repo fails with warning (will attach prodlog):
OST0005: Fetch summary failed. Reason: GLib.Error('Server returned status 404: Not Found', 'g-io-error-quark', 1)
The rhel-atomic-host-ostree synchronizes ok with default settings, but when custom depth is set, the synchronization fails this time with:
OST0006: Pulling local refs failed. Reason: GLib.Error('No such file or directory', 'g-io-error-quark', 1)
This seems to apply only to RH trees, custom Fedora tree syncs as expected with various depth settings
Seen in 6.5 snap 1, related packages:
I'm not sure if this is a duplicate of bug 1645067 as I can't reproduce 1645067 upstream, but I can reproduce this BZ(1645017).
I filed an issue on pulp here https://pulp.plan.io/issues/4276
Brad, can we remove the duplication?
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
*** This bug has been marked as a duplicate of bug 1625783 ***
The Pulp upstream bug status is at CLOSED - DUPLICATE. Updating the external tracker on this bug.
Re-opening based upon comment 6. Also, removing pulp redmine 4276 & adding 3999.
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Moving this back to POST until 2.18.1 and there is a new release of pulp-ostree.
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Verified in Satellite 6.5.0 Snap 22.
Red Hat Enterprise Linux Atomic Host Beta RPMs x86_64 now syncs successfully.
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.