Created attachment 958163 [details] please note that "blank line" in interval drop-down selection Description of problem: when creating a sync_plan the interval drop down contains a blank line. And this is the default selection. Earlier I think 'none' was set as default option. Since interval field is not mandatory, So when I create a sync_plan without specifying any sync interval, UI throws error below interval field: "is not included in the list" production.log: ---- Processing by Katello::Api::V2::SyncPlansController#create as JSON Parameters: {"startDate"=>"2014-11-17T05:51:14.336Z", "interval"=>{"id"=>"none", "value"=>"[FILTERED]"}, "name"=>"myplan", "sync_date"=>"Mon Nov 17 2014 11:21:00 GMT+0530 (IST)", "api_version"=>"v2", "organization_id"=>"1", "sync_plan"=>{"name"=>"myplan", "sync_date"=>"Mon Nov 17 2014 11:21:00 GMT+0530 (IST)", "interval"=>{"id"=>"none", "value"=>"[FILTERED]"}}} ActiveRecord::RecordInvalid interval: ["is not included in the list"] Completed 422 Unprocessable Entity in 28ms (Views: 0.4ms | ActiveRecord: 1.4ms) ---- Version-Release number of selected component (if applicable): zstream 6.0.6 * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23.1-1.el6.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23.1-1.el6.noarch * candlepin-tomcat6-0.9.23.1-1.el6.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.49-1.el6sat.noarch * foreman-compute-1.6.0.49-1.el6sat.noarch * foreman-gce-1.6.0.49-1.el6sat.noarch * foreman-libvirt-1.6.0.49-1.el6sat.noarch * foreman-ovirt-1.6.0.49-1.el6sat.noarch * foreman-postgresql-1.6.0.49-1.el6sat.noarch * foreman-proxy-1.6.0.30-1.el6sat.noarch * foreman-selinux-1.6.0.15-1.el6sat.noarch * foreman-vmware-1.6.0.49-1.el6sat.noarch * katello-1.5.0-30.el6sat.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.64-1.el6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-8.el6.x86_64 * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.4.3-0.1.beta.el6sat.noarch * pulp-nodes-parent-2.4.3-0.1.beta.el6sat.noarch * pulp-puppet-plugins-2.4.3-1.el6sat.noarch * pulp-puppet-tools-2.4.3-1.el6sat.noarch * pulp-rpm-plugins-2.4.3-1.el6sat.noarch * pulp-selinux-2.4.3-1.el6sat.noarch * pulp-server-2.4.3-1.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch * rubygem-hammer_cli-0.1.1-12.el6sat.noarch * rubygem-hammer_cli_foreman-0.1.1-16.el6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch * rubygem-hammer_cli_import-0.10.4-1.3.el6sat.noarch * rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Go to Content-Sync Plan 2. create New 3. Enter plan name only and click on save Actual results: The default selection is blank line Expected results: sync interval should include none as default option instead of blank line. Since this is not a mandatory field so without selecting any option, UI should create sync_plan successfully Additional info:
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Created attachment 958164 [details] on creating sync_plan with default interval selection, throws "interval: ["is not included in the list"]"
This is fixed in master, I believe via https://github.com/Katello/katello/pull/4737.
Created attachment 990802 [details] syncplan no longer has blank option and takes hourly as deafult syncplan no longer has blank option and takes hourly as deafult
This bug is slated to be released with Satellite 6.1.
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/RHSA-2015:1592