Created attachment 991113 [details] sync status incorrect Description of problem: Sync status displays irrelevant status Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150210.0 How reproducible: Always Steps to Reproduce: 1. Create a custom product and add a repo (preferably a large repo) 2. Start syncing the product 3. Navigate to the Product -> Repositories tab Actual results: Sync status shows 'Pending ago' Expected results: Sync status should show 'Pending' Additional info: screenshot attached
*** Bug 1223113 has been marked as a duplicate of this bug. ***
*** Bug 1232403 has been marked as a duplicate of this bug. ***
Created redmine issue http://projects.theforeman.org/issues/11646 from this bug
Katello PR: https://github.com/Katello/katello/pull/5456
Upstream bug component is WebUI
Moving to POST since upstream bug http://projects.theforeman.org/issues/11646 has been closed ------------- Brad Buckingham Applied in changeset commit:katello|3aadd66ba506f03f4fc2b562654aca0e725c2353.
*** This bug is verified in upstream. This fix should eventually land in future downstream builds *** Version Tested: # rpm -qa | grep foreman foreman-proxy-1.11.0-0.develop.201510201341git00875b3.el7.noarch foreman-selinux-1.11.0-0.develop.201510071426git6234447.el7.noarch tfm-rubygem-hammer_cli_foreman_bootdisk-0.1.3-3.el7.noarch tfm-rubygem-foreman_docker-1.4.1-2.fm1_10.el7.noarch foreman-debug-1.11.0-0.develop.201510271601git4e08a71.el7.noarch foreman-compute-1.11.0-0.develop.201510271601git4e08a71.el7.noarch foreman-release-scl-1-1.el7.x86_64 foreman-gce-1.11.0-0.develop.201510271601git4e08a71.el7.noarch tfm-rubygem-foreman_gutterball-0.0.1-3.el7.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-client-1.0-1.noarch tfm-rubygem-foreman_discovery-4.1.2-1.fm1_11.el7.noarch foreman-vmware-1.11.0-0.develop.201510271601git4e08a71.el7.noarch tfm-rubygem-foreman_hooks-0.3.9-1.el7.noarch tfm-rubygem-foreman-tasks-0.7.6-1.fm1_10.el7.noarch tfm-rubygem-hammer_cli_foreman_tasks-0.0.8-1.el7.noarch hp-z600-01.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch foreman-ovirt-1.11.0-0.develop.201510271601git4e08a71.el7.noarch foreman-1.11.0-0.develop.201510271601git4e08a71.el7.noarch tfm-rubygem-hammer_cli_foreman_docker-0.0.3-4.el7.noarch foreman-release-1.11.0-0.develop.201510271601git4e08a71.el7.noarch foreman-libvirt-1.11.0-0.develop.201510271601git4e08a71.el7.noarch foreman-postgresql-1.11.0-0.develop.201510271601git4e08a71.el7.noarch tfm-rubygem-hammer_cli_foreman-0.4.0-1.201510201150gitab068d9.el7.noarch tfm-rubygem-foreman_bootdisk-6.0.0-2.fm1_10.el7.noarch steps: 1. Create a custom product and add a repo (preferably a large repo) 2. Start syncing the product 3. Navigate to the Product -> Repositories tab Sync status should show 'Pending'
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:1500