Created attachment 569602 [details] Log Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Created provider account for rhevm and vsphere 2.Upload a fedora 32 bit image from conductor 2.Image build failed for rhevm but for vsphere it got successfully completed(PFA: log) Actual results: Observed that in conductor both the providers was having only "build" button enabled(PFA: no push button.png) Expected results: It is expected to have the push button enabled for the provider (which had a successful image build) Additional info: [root@dell-pe2950-01 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-41.el6.noarch aeolus-configure-2.5.0-18.el6.noarch rubygem-aeolus-cli-0.3.0-13.el6.noarch aeolus-all-0.8.0-41.el6.noarch rubygem-aeolus-image-0.3.0-12.el6.noarch aeolus-conductor-0.8.0-41.el6.noarch aeolus-conductor-daemons-0.8.0-41.el6.noarch
Created attachment 569603 [details] no push button
Created attachment 569604 [details] log
updating the steps Steps to Reproduce: 1.Created provider account for rhevm and vsphere 2.Upload a fedora 32 bit image from conductor 3.Clicked "build all" button 4.Image build failed for rhevm but for vsphere it got successfully completed(PFA: log) Actual results: Observed that in conductor both the providers was having only "build" button enabled(PFA: no push button.png) Expected results: It is expected to have the push button enabled for the provider (which had a successful image build)
I noticed this behaviour but was thinking it was part of bug 801199, it could be fixed there as it is in modified. Adding ifarkas for comment.
I tried to reproduce the issue with and without the patch for 801199 and it seems to me that the patch fixes this one, too.
Setting this to on_qa and verified with the fixes for bug 801199