Description of problem: Push all button is now visible on Image page if there is latest build even if that latest build have no target images. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. create new image 2. build image for provider 3. see push all button 4. delete image for provider 5. still see push all button even if there is no image to push Actual results: still see push all button even if there is no image to push Expected results: push all button should disapear Additional info: When displaying push all button one should check not only for latest build for selected image but also if that build has any target images built (ready to push)
What happens when you press the button?
From the user point of view nothing - only page is reloaded.
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-March/009450.html
This issue has been fixed. Please verify the commit e562208b3071344971214ec7a72f461f9a198628
e562208b3071344971214ec7a72f461f9a198628 is only in master branch as of this writing.
-Push all button is not visible till atleast a single provider has completed image building process. -A Provider now has a builed image.Pressing "push all" button after this results in pushing for that provider only. -Deletion of image after it is pushed,results in disappeared "Push all" button. Above observation satisfy the expectation from the fix.Marking as verified. [root@dhcp201-113 ~]# rpm -qa|grep aeolus rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-all-0.13.8-1.el6cf.noarch aeolus-conductor-0.13.8-1.el6cf.noarch rubygem-aeolus-cli-0.7.1-1.el6cf.noarch aeolus-configure-2.8.6-1.el6cf.noarch aeolus-conductor-daemons-0.13.8-1.el6cf.noarch aeolus-conductor-doc-0.13.8-1.el6cf.noarch
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. http://rhn.redhat.com/errata/RHEA-2012-1516.html