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.
Bug 1726811 - Changing download policy fails with error Validation failed: Upstream username and password may only be set on custom repositories
Summary: Changing download policy fails with error Validation failed: Upstream usernam...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: 6.5.0
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: 6.5.2
Assignee: Justin Sherrill
QA Contact: vijsingh
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-03 19:46 UTC by Mike McCune
Modified: 2019-10-30 17:02 UTC (History)
8 users (show)

Fixed In Version: tfm-rubygem-katello-3.10.0.54-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1674463
Environment:
Last Closed: 2019-08-06 14:37:33 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 26895 0 None None None 2019-07-03 19:47:02 UTC
Foreman Issue Tracker 27279 0 None None None 2019-07-17 13:25:42 UTC
Red Hat Product Errata RHBA-2019:2363 0 None None None 2019-08-06 14:37:43 UTC

Comment 4 Bryan Kearney 2019-07-03 20:06:08 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/26895 has been resolved.
Comment 7 Justin Sherrill 2019-07-17 13:25:42 UTC 
added other issue
Comment 8 vijsingh 2019-07-17 13:27:49 UTC 
ON_QA Failed.

@Satellite 6.5.1 snap 1.0


Works fine:

 - Save credential in Browser
 - Enable RHEL 7Server RPMs or create a Custom repo
 - Able to change the download policy from On Demand to Immediate/Background 


Not works:
 
 - Save credential in Browser
 - Create a Custom repo with checksum type(sha256) and download policy(Immediate) and save it.
 - Now try to change the download policy from 'Immediate' to 'Background' and it fails with error "An error occurred saving the Repository: Upstream password requires upstream username be set" 


Hence as per above looks a partial fix.
Comment 9 Mike McCune 2019-07-24 15:56:24 UTC 
https://projects.theforeman.org/issues/27279 is merged, moving to POST
Comment 12 vijsingh 2019-07-31 11:39:45 UTC 
ON_QA Verified.

@Satellite 6.5.1 snap 1.0


Steps/Observation:

 1)
 - Save credential in Browser
 - Enable RHEL 7Server RPMs or create a Custom repo
 - Able to change the download policy from On Demand to Immediate/Background 

 2) 
 - Save credential in Browser
 - Create a Custom repo with checksum type(sha256) and download policy(Immediate) and save it.
 - Able to change the download policy from 'Immediate' to 'Background'.
Comment 14 vijsingh 2019-07-31 11:42:07 UTC 
Apologies ..Correcting ...

ON_QA Verified @Satellite 6.5.2 Snap 2.0
Comment 17 errata-xmlrpc 2019-08-06 14:37:33 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, 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/RHBA-2019:2363
Note You need to log in before you can comment on or make changes to this bug.