Red Hat Bugzilla – Bug 1096407
Creating a sync plan from the web UI always uses the time when you first opened the page
Last modified: 2017-02-23 16:17:29 EST
Description of problem: When you use UI to create a new sync plan, no matter what time you choose for your plan, the data that gets saved is the datetime when you first opened the Sync Plan. For example, if you open the sync plan page, the time widgets should display your current time. If you try to modify this time and set it a few minutes ahead and save it, when you check your sync plan you'll see that it will display the current time when you first opened that page and not what you chose. Version-Release number of selected component (if applicable): * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.7-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.7-1.el6_5.noarch * candlepin-tomcat6-0.9.7-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.6.0.7-1.el6sat.noarch * foreman-compute-1.6.0.7-1.el6sat.noarch * foreman-gce-1.6.0.7-1.el6sat.noarch * foreman-libvirt-1.6.0.7-1.el6sat.noarch * foreman-ovirt-1.6.0.7-1.el6sat.noarch * foreman-postgresql-1.6.0.7-1.el6sat.noarch * foreman-proxy-1.6.0.4-1.el6sat.noarch * foreman-selinux-1.5.0-0.develop.el6sat.noarch * foreman-vmware-1.6.0.7-1.el6sat.noarch * katello-1.5.0-22.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.5-1.el6sat.noarch * katello-installer-0.0.37-1.el6sat.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-plugins-0.2-1.el6sat.noarch * pulp-nodes-common-2.3.1-0.4.beta.el6sat.noarch * pulp-nodes-parent-2.3.1-0.4.beta.el6sat.noarch * pulp-puppet-plugins-2.3.1-0.4.beta.el6sat.noarch * pulp-rpm-plugins-2.3.1-0.4.beta.el6sat.noarch * pulp-selinux-2.3.1-0.4.beta.el6sat.noarch * pulp-server-2.3.1-0.4.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.0.8-1.el6sat.noarch * rubygem-hammer_cli-0.1.0-12.el6sat.noarch * rubygem-hammer_cli_foreman-0.1.0-12.el6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.2-5.el6sat.noarch * rubygem-hammer_cli_katello-0.0.3-22.el6sat.noarch How reproducible: Steps to Reproduce: 1. Use the we ui to create a new sync plan and set the datetime ahead by several minutes 2. Save it 3. View it Actual results: Saved time does not match what you choose Expected results: Additional info:
*** Bug 1082632 has been marked as a duplicate of this bug. ***
PR: https://github.com/Katello/katello/pull/4232
commit 763b2930b096397edb5eee82fe63b9915a97ac18 Merge: 3b53723 938d01b Author: Walden Raines <walden@redhat.com> Date: Tue Jun 10 10:04:19 2014 -0400 Merge pull request #4232 from waldenraines/5162 Fixes #5162/BZ1096407 - fix setting of sync time for new sync plans. commit 938d01b953a63214b3ebff23bf8c716438727466 Author: Walden Raines <walden@redhat.com> Date: Mon Jun 9 11:46:58 2014 -0400 Fixes #5162/BZ1096407 - fix setting of sync time for new sync plans.
Satellite-6.0.3-RHEL-6-20140612.1 (beta snap 9 compose 2) Created sync plan for product in UI and current time was saved instead of what was set.
*** Bug 1117765 has been marked as a duplicate of this bug. ***
Verified. Version Tested: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.19-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.19-1.el6_5.noarch * candlepin-tomcat6-0.9.19-1.el6_5.noarch * elasticsearch-0.90.10-4.el6sat.noarch * foreman-1.6.0.29-1.el6sat.noarch * foreman-compute-1.6.0.29-1.el6sat.noarch * foreman-gce-1.6.0.29-1.el6sat.noarch * foreman-libvirt-1.6.0.29-1.el6sat.noarch * foreman-ovirt-1.6.0.29-1.el6sat.noarch * foreman-postgresql-1.6.0.29-1.el6sat.noarch * foreman-proxy-1.6.0.21-1.el6sat.noarch * foreman-selinux-1.6.0-8.el6sat.noarch * foreman-vmware-1.6.0.29-1.el6sat.noarch * katello-1.5.0-27.el6sat.noarch * katello-ca-1.0-1.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-installer-0.0.56-1.el6sat.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-0.3-3.el6sat.noarch * pulp-nodes-common-2.4.0-0.23.beta.el6sat.noarch * pulp-nodes-parent-2.4.0-0.23.beta.el6sat.noarch * pulp-puppet-plugins-2.4.0-0.23.beta.el6sat.noarch * pulp-puppet-tools-2.4.0-0.23.beta.el6sat.noarch * pulp-rpm-plugins-2.4.0-0.23.beta.el6sat.noarch * pulp-selinux-2.4.0-0.23.beta.el6sat.noarch * pulp-server-2.4.0-0.23.beta.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
This was delivered with Satellite 6.0 which was released on 10 September 2014.
Moving to POST since upstream bug http://projects.theforeman.org/issues/5162 has been closed ------------- Walden Raines https://github.com/Katello/katello/pull/4232 ------------- Walden Raines Applied in changeset katello|commit:938d01b953a63214b3ebff23bf8c716438727466.
This is fixed upstream already but is not in SAT6 GA.
Verified on latest 6.1 build: * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.43-1.el6.noarch * candlepin-common-1.0.21-1.el6.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.43-1.el6.noarch * candlepin-tomcat6-0.9.43-1.el6.noarch * elasticsearch-0.90.10-7.el6.noarch * foreman-1.7.2.6-1.el6_6sat.noarch * foreman-compute-1.7.2.6-1.el6_6sat.noarch * foreman-debug-1.7.2.6-1.el6_6sat.noarch * foreman-gce-1.7.2.6-1.el6_6sat.noarch * foreman-libvirt-1.7.2.6-1.el6_6sat.noarch * foreman-ovirt-1.7.2.6-1.el6_6sat.noarch * foreman-postgresql-1.7.2.6-1.el6_6sat.noarch * foreman-proxy-1.7.2.3-1.el6_6sat.noarch * foreman-selinux-1.7.2.8-1.el6_6sat.noarch * foreman-vmware-1.7.2.6-1.el6_6sat.noarch * katello-2.2.0.5-1.el6_6sat.noarch * katello-certs-tools-2.2.1-1.el6_6sat.noarch * katello-common-2.2.0.5-1.el6_6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-2.2.0.7-1.el6_6sat.noarch * katello-installer-base-2.2.0.7-1.el6_6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.39-8.el6.x86_64 * pulp-docker-plugins-0.2.2-1.el6_6sat.noarch * pulp-katello-0.3-4.el6sat.noarch * pulp-nodes-common-2.6.0-0.7.beta.el6_6sat.noarch * pulp-nodes-parent-2.6.0-0.7.beta.el6_6sat.noarch * pulp-puppet-plugins-2.6.0-0.7.beta.el6sat.noarch * pulp-puppet-tools-2.6.0-0.7.beta.el6sat.noarch * pulp-rpm-plugins-2.6.0-0.7.beta.el6_6sat.noarch * pulp-selinux-2.6.0-0.7.beta.el6_6sat.noarch * pulp-server-2.6.0-0.7.beta.el6_6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-ldap_fluff-0.3.2-1.el6_6sat.noarch * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.3.0-1.el6_6sat.noarch * rubygem-hammer_cli-0.1.4.3-1.el6_6sat.noarch * rubygem-hammer_cli_foreman-0.1.4.4-1.el6_6sat.noarch * rubygem-hammer_cli_foreman_bootdisk-0.1.2.4-1.el6_6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch * rubygem-hammer_cli_gutterball-0.0.1.2-1.el6_6sat.noarch * rubygem-hammer_cli_import-0.10.6.2-1.el6_6sat.noarch * rubygem-hammer_cli_katello-0.0.7.2-1.el6_6sat.noarch
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