Bug 781482

Summary: no feedback for image build/push failures
Product: [Retired] CloudForms Cloud Engine Reporter: Dave Johnson <dajohnso>
Component: aeolus-conductorAssignee: Ian McLeod <imcleod>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: high Docs Contact:
Priority: medium    
Version: 1.0.0CC: akarol, athomas, deltacloud-maint, hbrock, morazi, redakkan, slinaber, ssachdev, whayutin
Target Milestone: 1.1.3Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
build_status
none
push failure none

Description Dave Johnson 2012-01-13 15:24:49 UTC
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.

Comment 1 Angus Thomas 2012-01-24 17:27:14 UTC
*** Bug 772285 has been marked as a duplicate of this bug. ***

Comment 2 Imre Farkas 2012-01-27 14:32:35 UTC
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-January/008427.html

Comment 3 Imre Farkas 2012-01-30 15:23:27 UTC
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

Comment 4 Steve Linabery 2012-01-31 16:05:37 UTC
6f4ae15 in aeolus-conductor-0.8.0-16

Comment 5 Steve Linabery 2012-01-31 16:07:55 UTC
b459e42 in rubygem-aeolus-image-0.3.0-6

Comment 6 Shveta 2012-02-07 14:47:18 UTC
Created attachment 559972 [details]
build_status

Comment 7 Shveta 2012-02-07 14:50:37 UTC
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

Comment 8 Imre Farkas 2012-02-09 12:43:38 UTC
Patch has been posted: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008744.html

Comment 9 Imre Farkas 2012-02-09 14:14:19 UTC
The image status update issue has been fixed. Please verify the commit 2bbd6bb57f3bedb2ac89fe6e891218da7912f55c

Comment 10 Dave Johnson 2012-02-09 17:26:29 UTC
*** Bug 788493 has been marked as a duplicate of this bug. ***

Comment 11 Shveta 2012-02-13 09:03:08 UTC
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

Comment 12 Dave Johnson 2012-02-14 19:11:19 UTC
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.

Comment 13 Dave Johnson 2012-02-14 19:22:32 UTC
Created attachment 562021 [details]
push failure

Comment 14 Angus Thomas 2012-02-22 12:28:16 UTC
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.

Comment 15 wes hayutin 2012-02-22 23:46:50 UTC
moving version to 1.0.0 .  version = found in version

Comment 16 jrd 2012-08-15 15:46:32 UTC
Ian?

Comment 17 Mike Orazi 2012-08-15 15:51:19 UTC
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.