Description of problem: ===================================== Summary pretty much says it all. If a image build/push fails, there is no feedback for the user forcing them to go to search log files assuming they have access to the command line which is probably not going to be the case in most field deployments.
*** Bug 772285 has been marked as a duplicate of this bug. ***
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008427.html
Labels added to images#show page containing counters about the failed build/push attempts. It is only visible if there is at least one failed build/push attempt in imagefactory .This works until imagefactory is restarted (history of built/pushed images returned by imagefactory and is lost after restart), but there is nothing we can do with this. Please verify the commit 6f4ae15f3cb07a78c89f9144628f4cafb73c8008
6f4ae15 in aeolus-conductor-0.8.0-16
b459e42 in rubygem-aeolus-image-0.3.0-6
Created attachment 559972 [details] build_status
So the build and push status are now displayed in conductor/images page as well as deployable page but it doesn't refresh. i.e i build for a provider and it showed status "new" for few minutes after that it disappeared , refresh page and status is displayed again rpm -qa|grep aeolus aeolus-conductor-daemons-0.8.0-21.el6.noarch aeolus-configure-2.5.0-12.el6.noarch aeolus-conductor-doc-0.8.0-21.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-conductor-0.8.0-21.el6.noarch aeolus-all-0.8.0-21.el6.noarch
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008744.html
The image status update issue has been fixed. Please verify the commit 2bbd6bb57f3bedb2ac89fe6e891218da7912f55c
*** Bug 788493 has been marked as a duplicate of this bug. ***
Build/Push Status is properly displayed without refreshing Verified w/ rpm -qa|grep rubygem-json rubygem-json-1.4.6-5.el6.x86_64 [root@qe-blade-08 ~]# rpm -qa|grep aeolus aeolus-conductor-0.8.0-25.el6.noarch aeolus-conductor-doc-0.8.0-25.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-conductor-daemons-0.8.0-25.el6.noarch aeolus-configure-2.5.0-12.el6.noarch aeolus-all-0.8.0-25.el6.noarch
Reopening this one... For starters, there still is no feedback when a build failure occurs... at least in the scenario where the template install url is bad. But the major reason for reopening is that this is not enough feedback for the user who is most circumstances WILL NOT have command line access to troubleshoot the failure.
Created attachment 562021 [details] push failure
This is dependent on the addition of diagnostic information to the imagefactory REST API, which, I#m told, is scheduled for the development leading up to 1.0.
moving version to 1.0.0 . version = found in version
Ian?
This appears to be a 2.0.0 feature requiring updates to the imagefactory api. I think it got auto-approved because we didn't clear the acks before kicking it to 1.1.