Bug 1930789

Summary: pulp3: creating repo with background Download Policy fails
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.9.0CC: jsherril, pcreech, smallamp
Target Milestone: 6.9.0Keywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: tfm-rubygem-katello-3.18.1.15-1,tfm-rubygem-katello-3.18.1.17-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-04-21 13:11:14 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
new repo with background download fail on creation none

Description Stephen 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
Comment 1 Justin Sherrill 2021-02-25 14:25:35 UTC 
Created redmine issue https://projects.theforeman.org/issues/31967 from this bug
Comment 5 Justin Sherrill 2021-03-16 15:35:46 UTC 
I'm not sure what happened, the associated MR has a commit with this BZ and part of my upstream change, but not the full change.
Comment 11 errata-xmlrpc 2021-04-21 13:11:14 UTC 
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