Description of problem: When creating a new Product Repo, the "Download Policy" field is unpopulated by default. Furthermore, continuing on w/o selecting a Download policy defaults to "On Demand", which is the last option in the dropdown. Version-Release number of selected component (if applicable): SNAP 6 How reproducible: Steps to Reproduce: 1. Install fresh satellite, start creating product repos. 2. Observe the "Download Policy" field which is blank. Do not select anything 3. Submit Actual results: * Repo can be created w/o immediately/knowingly selecting any Download Policy * The Download policy selected is the last one in the list, not even the first one. Expected results: A bit more intuitive behavior, at least an option prepopulated in there. Additional info: < mmccune> cswiii: im pretty sure it will default to the site-wide default in Settings This is fine, but in this case it means we should pre-select/autopopulate the site-wide default in the dropdown. This is a really small thing, but it is going to confuse new user, especially those trying out the new feature.
*** Bug 1315365 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/14622 from this bug
This supersedes https://bugzilla.redhat.com/show_bug.cgi?id=1323769 which is marked as Beta. So I'm moving this to Beta.
Moving to POST since upstream bug http://projects.theforeman.org/issues/14622 has been closed ------------- Anonymous Applied in changeset commit:katello|f12bb40c32fad1d6655a131c8e81a97a0afa3fab.
VERIFIED with sat62-snap9.2 Now the download policy for the custom repos being created will be picked up depending upon the global download policy set, which is Administer-->Settings-->Katello-->Default download policy. a) created a custom repo with "immediate" set as "default download policy" in global setting and the same reflected for the custom repo as default. b) created a custom repo with "on_demand" set as "default download policy" in global setting and the same reflected for the custom repo as default.
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-2016:1501