Red Hat Bugzilla – Bug 1246262
sync plan dates saved incorrectly if I dont use the calendar widget
Last modified: 2016-07-27 05:16:47 EDT
Description of problem: sync plan dates saved incorrectly if I dont use the calendar widget Version-Release number of selected component (if applicable): Sat 6.1 GA Snap 14 How reproducible: Always Steps to Reproduce: 1. Navigate to Content -> Sync Plans 2. Click 'New Sync Plan' 3. Enter name=syncplan1, description=test sync plan, Interval=hourly 4. Enter a future date example in YYYY-MM-DD format: 2015-10-01 (type this text in the text box and do not select from the calendar widget) 5. Leave Start Time with default (current time) Actual results: Sync plan is created with start date of 2015-09-30 (One day less than what I entered) Expected results: Sync plan should be created with a requested start date and not one day prior. Additional info: This same date works fine when I select the date from the calendar widget. This fails in QE automation for this same reason.
Created redmine issue http://projects.theforeman.org/issues/11295 from this bug
VERIFIED: # rpm -qa | grep foreman dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch foreman-release-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-ovirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-libvirt-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-postgresql-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch dell-pem600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch dell-pem600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-2.noarch tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch foreman-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch foreman-debug-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-proxy-1.11.0-0.develop.201511111339git7cbe47a.el7.noarch foreman-compute-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201511111650gitdda13df.el7.noarch foreman-gce-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-vmware-1.11.0-0.develop.201511111740gitb2a959e.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch steps: 1. Navigate to Content -> Sync Plans 2. Click 'New Sync Plan' 3. Enter name=syncplan1, description=test sync plan, Interval=hourly 4. Enter a future date example in YYYY-MM-DD format: 2015-10-01 (type this text in the text box and do not select from the calendar widget) 5. Leave Start Time with default (current time) Sync plan should be created with a requested start date.
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