Bug 785892

Summary: unable to build/push to individual providers after importing template via webui
Product: [Retired] CloudForms Cloud Engine Reporter: wes hayutin <whayutin>
Component: aeolus-conductorAssignee: Scott Seago <sseago>
Status: CLOSED ERRATA QA Contact: wes hayutin <whayutin>
Severity: high Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, slinaber, ssachdev, sseago
Target Milestone: beta   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://10.16.185.95/conductor/images/c2b13310-4b7e-11e1-83e6-52540042446c
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-15 22:25:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
build_individual_provider none

Description wes hayutin 2012-01-30 20:32:27 UTC
Description of problem:

1. nav to "Environments -> new image"
2. upload a template from file or url
3. add or do not add a deployable automatically (doesnt matter)

At this point the only option is to "rebuild" for all providers.


As a user.. you are looking to build for a specific provider
As a user.. you want to push to a specific provider after a build completes


see screenshot

Comment 1 Hugh Brock 2012-02-02 14:27:47 UTC
Checked with PM: Conclusion is for 1.0 we don't want to get too far into the "build for this particular provider type" feature set because we're promising something (repo versioning, build consistency) that we can't deliver. So no per-provider build button for 1.0. However we will change the wording on the button so that it just says "Build", which should at least reduce some confusion.

Comment 2 wes hayutin 2012-02-02 21:29:22 UTC
the feature has been there.. however uploading via the webui exposed a bug.

the feature works if you use cli tools

Comment 3 Scott Seago 2012-02-02 21:33:52 UTC
Hugh -- if we actually intend to _not_ allow builds to be only uploaded to a subset of providers, we've got a lot of code to remove, as the existing code already allows pushing at various times, deleteing/recreating builds, and as Wes says, the  cli allows even more flexibility.

In addition, when you add providers later, the 'build' option remains, so we have the same repo versioning/consistency issues.

In any case I've already sent a patch on-list that resolves this specific bug:
https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008600.html

(sorry I referenced  the wrong bz in the patch on list -- I'll fix that before pushing it)

If we really don't want this patch, then open a separate bug to remove several existing UI and cli elements, but that's a fair amount of work to do something that essentially removes functionality.

Comment 4 Scott Seago 2012-02-06 19:10:53 UTC
Fix pushed with commit dc9e671a71cbc253af987d7f2078709c99963410

Comment 5 Steve Linabery 2012-02-14 18:45:06 UTC
dc9e671 in aeolus-conductor-0.8.0-27

Comment 6 Shveta 2012-02-16 10:33:51 UTC
Created attachment 562457 [details]
build_individual_provider

Comment 7 Shveta 2012-02-16 10:35:14 UTC
Verified w/
rpm -qa|grep aeolus
aeolus-conductor-doc-0.8.0-27.el6.noarch
aeolus-conductor-daemons-0.8.0-27.el6.noarch
aeolus-configure-2.5.0-13.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-all-0.8.0-27.el6.noarch
aeolus-conductor-0.8.0-27.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch

Comment 8 errata-xmlrpc 2012-05-15 22:25:38 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHEA-2012-0583.html