Bug 769048

Summary: After an image build error, imagefactory does not respond to additional build requests without a service restart
Product: [Retired] CloudForms Cloud Engine Reporter: chris alfonso <calfonso>
Component: imagefactoryAssignee: Steve Loranz <sloranz>
Status: CLOSED CURRENTRELEASE QA Contact: Martin Kočí <mkoci>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, brad, dajohnso, deltacloud-maint, dgao, hbrock, nobody, ssachdev, whayutin
Target Milestone: rc   
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:

Description chris alfonso 2011-12-19 18:39:10 UTC 
Description of problem:
After an image build failure, for any reason, imagefactory will respond to build requests and the imagefactory.log will immediately report completion of the build request, but the build actually never occurs.

Version-Release number of selected component (if applicable):
imagefactory-1.0.0rc1-2.el6.noarch.rpm

How reproducible:
Make the build fail for any reason (repo not available as an example)

Steps to Reproduce:
1. Build an image with aeolus-cli, and watch it fail in the imagefactory.log
2. Try the build again (after correcting whatever you did to make the first build fail)
3. Observe the imagefactory.log, it will report successfully processing the build request, but it doesn't actually do anything.
  
Actual results:
Imagefactory seems to be in a wedged state.

Expected results:
The subsequent build requests should be processed.
Comment 1 Steve Loranz 2011-12-20 15:53:22 UTC 
What version of RHEL or Fedora are you running imagefactory on?
Comment 2 Steve Loranz 2011-12-20 16:00:52 UTC 
Also, can I see your imagefactory log?
Comment 3 Steve Loranz 2011-12-23 19:27:42 UTC 
This is fixed in 5d7829b5c0ca8203ae74b3454b8566bbfafbe95a

https://github.com/aeolusproject/imagefactory/commit/5d7829b5c0ca8203ae74b3454b8566bbfafbe95a
Comment 4 Shveta 2011-12-27 16:50:34 UTC 
Build and pushed with a wrong repo .
Push fails .

Built again with correct template -- image is built successfully. 


Verified in 
rpm -qa|grep aeolus
aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.noarch
aeolus-conductor-daemons-0.8.0-0.20111222233342gitd98cb57.el6.noarch
rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.noarch
rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.noarch
aeolus-configure-2.5.0-0.20111222173430git17b704a.el6.noarch
aeolus-conductor-doc-0.8.0-0.20111222233342gitd98cb57.el6.noarch