Description of problem: Ostree repo sync fails with 'OverflowError: MongoDB can only handle up to 8-byte ints' Version-Release number of selected component (if applicable): Satellte 6.4.1 Snap 2.0 How reproducible: Awlays Steps to Reproduce: 1. Create repository with following details: on GUI: Content => Product => <Select custom product> => Repositories => 'New Repository' => Select 'Type = Ostree' and 'Upstream URL = https://kojipkgs.fedoraproject.org/atomic/27/' Refer attached screenshots for more details 2. Now sync the same repository. 3. Check the tasks status as below: Monitor => Tasks => click on "Synchronize repository 'xxxxxxxxxxx'" Actual results: Repo sync fails with error "PLP0000: MongoDB can only handle up to 8-byte ints" Expected results: Repository should sync successfully Additional info: - Same was working in earlier snap/version of 6.4 - Same is working fine with Satellite 6.5.0 snap 7.0 - Looks a regression
Created attachment 1513613 [details] Screenshot 1
Created attachment 1513614 [details] Screenshot 2
This was fixed in upstream here: https://pulp.plan.io/issues/3534 This will be included in Satellite 6.5 since 6.5 is on Pulp 2.18.
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
The Pulp upstream bug priority is at High. Updating the external tracker on this bug.
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
I don't think this is a regression but rather a bug caused by a change to the https://kojipkgs.fedoraproject.org/atomic/27/ repository. I am setting NEEDINFO to @jortel to confirm.
Verified: @Satellite 6.5.0 Snap 14 Steps/Observation: - Created repo as below: Content => Product => <Select custom product> => Repositories => 'New Repository' => Select 'Type = Ostree' and 'Upstream URL = https://kojipkgs.fedoraproject.org/atomic/27/' - Able to sync Ostree repo now.
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. https://access.redhat.com/errata/RHSA-2019:1222