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.
DescriptionJustin Sherrill
2016-03-07 14:51:00 UTC
Description of problem:
When creating a repo within the web UI, there are 4 options:
**BLANK**
on demand
background
immediate
If the user leaves it blank, the server default is selected, but:
a) this is not obvious as other fields on this page do not behave that way
b) There isn't any way for the user to know what the default is
Version-Release number of selected component (if applicable):
6.2.0 snap1
How reproducible:
always
Additional info:
A description for each policy on that page would be good to.
in 6.2.0 Snap5.1, leaving the download_policy blank doesn't pass the validation and returns:
"Download policy is not included in the list".
The weird side effect is that the invalid field with the error message is not highlighted in red so it's hard to spot why the validation failed.
The error is most probably caused by this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1320311