Bug 1108317
| Summary: | Puppet syncs through dynflow show no progress | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Justin Sherrill <jsherril> |
| Component: | WebUI | Assignee: | Justin Sherrill <jsherril> |
| WebUI sub component: | Katello | QA Contact: | jcallaha |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | unspecified | CC: | ahumbe, bbuckingham, cwelton, jcallaha, sthirugn |
| Version: | 6.0.3 | Keywords: | Triaged |
| Target Milestone: | Unspecified | ||
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| URL: | http://projects.theforeman.org/issues/8268 | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-12 05:09:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Justin Sherrill
2014-06-11 17:12:53 UTC
This is a usability issue. Atleast there should be a UI warning saying the progress bar will not work for puppet sync and also we can disable progress bar if possible. Created redmine issue http://projects.theforeman.org/issues/8268 from this bug Moving to POST since upstream bug http://projects.theforeman.org/issues/8268 has been closed ------------- Justin Sherrill Applied in changeset commit:katello|e3e8c5b04070f81912b658a51df6acded567acfe. *** 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 |