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.
DescriptionStephen Wadeley
2021-02-19 15:11:59 UTC
Created attachment 1758178[details]
new repo with background download fail on creation
Created attachment 1758178[details]
new repo with background download fail on creation
Description of problem:
After migrating to pulp3, trying to create a repo with download set to background fails
Version-Release number of selected component (if applicable):
Sat6.9 Snap 13
How reproducible:
not sure
Steps to Reproduce:
1. carry out pulp2 to pulp3 migration steps
2. Try to create repo with download policy set to background
3.
Actual results:
A pop-up error is displayed. See screen capture attached.
The task shows this error:
Error message: the server returns an error
HTTP status code: 400
Response headers: {"Date"=>"Fri, 19 Feb 2021 12:42:05 GMT", "Server"=>"gunicorn/20.0.4", "Content-Type"=>"application/json", "Vary"=>"Accept,Cookie", "Allow"=>"GET, POST, HEAD, OPTIONS", "X-Frame-Options"=>"SAMEORIGIN", "Content-Length"=>"52", "Via"=>"1.1 dhcp-2-116.vms.sat.rdu2.redhat.com", "Connection"=>"close"}
Response body: {"policy":["\"background\" is not a valid choice."]}
Expected results:
Background does say deprecated, but that implies it should still work
Either it works or a more user friendly error message is displayed
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.9 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:1313