Bug 785303

Summary: Checking of install location causes snapshot build to fail
Product: [Retired] CloudForms Cloud Engine Reporter: Brad P. Crochet <brad>
Component: imagefactoryAssignee: Ian McLeod <imcleod>
Status: CLOSED NOTABUG QA Contact: Martin Kočí <mkoci>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, brad, dajohnso, deltacloud-maint, dgao, hbrock, morazi, 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: 2014-03-26 14:05:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Brad P. Crochet 2012-01-27 22:18:37 UTC
When a snapshot build is performed, the install location is checked for validity. If this location is invalid, the snapshot build fails. Should this be checked for a snapshot build?

Comment 1 wes hayutin 2012-01-28 14:48:26 UTC
Please add the rpm version this was found in. Thanks

Comment 2 Brad P. Crochet 2012-01-30 13:57:38 UTC
RPM build is: imagefactory-1.0.0rc3_5_g1041f75-1.fc16.noarch

Comment 3 Ian McLeod 2012-02-01 18:58:41 UTC
We can certainly turn off this check for snapshot builds.  On the other hand, one could argue that it is important to use valid TDL (pointing to valid install locations) _even if_ you are doing a snapshot build, since ideally the TDL should also be capable of building locally for pushing to RHEV-M and vsphere.

This should not be a 1.0.0 blocker.

Wes and Brad, can you indicate if you really think this is a bug that needs to be fixed?  (Versus a feature that benefits users :-)

Comment 4 Brad P. Crochet 2012-02-02 15:44:57 UTC
This should not be a 1.0.0 blocker. 

The only reason I can think someone would want this is that they are doing only snapshot builds, and not planning to do local builds.

In this case, perhaps a "dummy" entry that signals "I don't care about this because I'll never use it"

Comment 5 Hugh Brock 2012-02-08 16:35:54 UTC
Moving to 1.1.0 -- doesn't sound to me like QE even really wants this fixed.

Comment 6 Mike Orazi 2012-08-15 16:54:33 UTC
This appears to have been auto-approved because flags weren't flipped prior to moving to 1.1.0?.  This is will be considered for a future release.

Comment 7 Ian McLeod 2014-03-26 14:05:26 UTC
Per my earlier comments in this bug, I consider this a feature.  Closing.