Red Hat Bugzilla – Bug 1120710
Sync Status start time and result progress bar get out of sync
Last modified: 2017-02-23 16:12:51 EST
Created attachment 918732 [details] screen shot Description of problem: Noticed while syncing RHEL 6 kickstart and Server RPMS that the start time jumps in value that is incorrect. During a long sync the start time is accurate but when the sync reaches then end the time jumps back to "1 minute ago" and then starts over. Also the status bar goes from 100% to 0% while it waits to update to "Sync Complete" Attaching a screen shot.
Created attachment 918733 [details] completed sync screen shot of when sync completed
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.
So this was largely fixed for GA, however i have noticed that the sync bar does not seem to update, will work on fixing.
Created redmine issue http://projects.theforeman.org/issues/8262 from this bug
Moving to POST since upstream bug http://projects.theforeman.org/issues/8262 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|7dd9236b00bba5fa33f683ee7db216a00c71d2e9.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** RHEL65 / RHEL7 Version Tested: foreman-proxy-1.8.0-0.develop.201411121327gitab6edc2.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-gce-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-selinux-1.8.0-0.develop.201410280941git10de1c5.el7.noarch foreman-vmware-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-release-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_discovery-1.4.0-2.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.3-2.201409091410git163c264.git.0.988ca80.el7.noarch foreman-postgresql-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_docker-0.2.0-2.el7.noarch rubygem-hammer_cli_foreman-0.1.3-1.201411121216git9381fc5.el7.noarch foreman-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-ovirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman-tasks-0.6.9-1.el7.noarch foreman-libvirt-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch foreman-compute-1.8.0-0.develop.201411131139git5cd6de6.el7.noarch ruby193-rubygem-foreman_bootdisk-4.0.0-1.el7.noarch yttrium.idmqe.lab.eng.bos.redhat.com-foreman-client-1.0-1.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7.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