Hide Forgot
Created attachment 551678 [details] Screenshot Description of problem: Version-Release number of selected component (if applicable): * aeolus-all-0.8.0-0.20111222233342gitd98cb57.el6.src.rpm * aeolus-conductor-0.8.0-0.20111222233342gitd98cb57.el6.src.rpm * aeolus-configure-2.5.0-0.20120104154940git196b80d.el6.src.rpm * rubygem-aeolus-cli-0.3.0-0.20111222173356git3cd6277.el6.src.rpm * rubygem-aeolus-image-0.3.0-0.20111222173411gitc13b654.el6.src.rpm How reproducible: Steps to Reproduce: 1. Login to conductor as the admin user 2. From the "Administer" <tab>, select "Environments", then choose "New Image" under the default Pool 3. Enter a valid image name, upload a valid system template (see attached), and choose "[X] Edit before saving", then select "Continue" 4. Uncheck "[ ] Automatically make '<my-image-name>' deployable." then select "Save Template" Actual results: At the resulting image screen, there is no option to build or push images to specific providers. The only option is to "Rebuild All". See attached screenshot. Expected results: I'm accustomed to having the ability to build and push to specific providers from the "Environments -> Images" screen (https://<my-conductor>/conductor/images/<image-id>) Additional info: * See attached system template. * Marking as blocks:ce-sprint as recommended by weshay
Created attachment 551679 [details] system_template.xml
I have not heard anything from Angus on this.. but is it possible there has been a design change and build/pushing can only occur from the equally confusing UI in https://server/conductor/catalogs/1/deployables/3 ? I am only guessing here.. but as it stands this is a regression
We don't support building for a specific provider, either when viewing the images listed unded Administer => Environments, or when viewing the details of a deployable. Instead, the deployable details view allows the admin to build, or push for any accounts on which those operations have not already been completed *for the current build*, and the view listing images under environments allows the admin to rebuild, from the template, for all applicable providers. Doing so would create a new build, selectable in the dropdown box. Plans for supporting as single-click build and push per provider account, for which we created UI mockups, we descoped for 1.0 because: - In the absence of a single build+push api call to imagefactory, it requires a delayed job implementation within Conductor to defer the push call until the build call has successfully completed. Conductor doesn't currently have a delayed job mechanism - Selecting a subset of available provider account to build/push for would require that we persist that selection for each deployable. We reached the freeze on new features on 1.0 before implementing that. All this will be revisited post 1.0, but the current behaviour won't change for the initial release.
Sounds like CLOSED->DEFERRED or version=1.1.0 is appropriate if comment#3 holds?
Angus.. I think the title of the bug is throwing you off here.. Here is what I am seeing... Template images that are imported via the webui are not listing the build/push links from page /conductor/images/$template-image-hash I think that is a regression.. I believe that was working.. Now.. If a deployable is created via the above workflow... The user is offered the ability to build/push via another page.. page = conductor/catalogs/1/deployables/$deployable# If I am able to build/push via the second URL the same template should have the links to build push via /conductor/images Something is not working in the puddle build for uplodated image templates. IMHO these two pages are quite confusing and should be revisited.. Moving back to Angus
*** This bug has been marked as a duplicate of bug 766191 ***