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.
DescriptionVladimír Sedmík
2021-07-22 23:03:42 UTC
Description of problem:
Sync of a file repository to a pulp3 capsule fails with this error:
null value in column "repository_version_id" violates not-null constraint
DETAIL: Failing row contains (537b49d4-37ee-44bc-b442-5ab587999800, 2021-07-22 22:40:36.019239+00, 2021-07-22 22:40:36.01926+00, file.file, f, t, null).
Version-Release number of selected component (if applicable):
6.10.0 snap 10
How reproducible:
always
Steps to Reproduce:
1. Have a SAT and pulp3 CAPS (with Immediate download policy)
2. Sync a file repo to the SAT (I used https://fixtures.pulpproject.org/file-large/)
3. Publish a CV with that repo and promote it to the Capsule LCE
4. Trigger at least one Optimized sync and then Complete sync
Actual results:
The Complete (and any consecutive) sync fails
Expected results:
Successful sync
Verified.
Tested on Satellite 6.10.0 Snap 14.0
Steps followed:
1. Have a SAT and pulp3 CAPS (with Immediate download policy)
2. Sync a file repo to the SAT (I used https://fixtures.pulpproject.org/file-large/)
3. Publish a CV with that repo and promote it to the Capsule LCE
4. Trigger at least one Optimized sync and then Complete sync
Observation:
Sync is successful without any errors
Comment 11pulp-infra@redhat.com
2021-08-26 17:16:19 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
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 (Moderate: Satellite 6.10 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-2021:4702