| Summary: | Unable to retrieve the target image id from build id for the comp. outline build from conductor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] CloudForms Cloud Engine | Reporter: | Rehana <redakkan> | ||||
| Component: | imagefactory | Assignee: | Ian McLeod <imcleod> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Rehana <aeolus-qa-list> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 1.0.0 | CC: | akarol, athomas, cpelland, deltacloud-maint, hbrock, morazi, ssachdev | ||||
| Target Milestone: | rc | Keywords: | FutureFeature | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Enhancement | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-03-26 14:12:25 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: |
|
||||||
This is expected behaviour. Target Images that are not complete are not listed. aeolus-image only lists completed target images. A reference (ID) to the new target image is displayed when a build is initially started. You can use this reference (ID) to check the status of the target image whilst the build is in progress. Once the build has completed. The target image is available and will be listed in the list --targetimages <build_id> command. Updating the comments, In this bug what i was trying to say is, user is not getting any Ids (like build id, target id,provider id) when he/she does an image build/push from Conductor. It will be better to show the build command output, image Build Target Image Target Status ----- ----- ------------ ------ ------ and push command output Target Image Provider Image Provider Account Status ----------- ------------- -------- ------ ------ like this in the rails.log(or any), so that these Ids can be used in future. As per the request, i have added detailed comment.(comment 2) After to speaking with Angus and Jan from Conductor team. It appears that this will require more than just a trivial change. As such, it's been suggest that this should be moved to 1.1 release. This is actually an RFE against a conductor component. Closing as it is not related to factory. |
Created attachment 567041 [details] Steps Description of problem: When the 'build operation" is going on the user is unable to retrieve the target image id from build id for the comp. outline build from conductor This was observed, when i tried to retrieve target id of an image (which is build from conductor) using CLI commands Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.Logged in to conductor 2.uploaded an image template from conductor 3.Click on "build" from conductor 4. Attached doc explain each steps (PFA> steps) 5. Actual results: The command "aeolus-image list --targetimages <build id>" Failed to retrieve the target id when the image build was going on..Once the build was completed, the command retrieves the targetimages. Expected results: when the image build was going on,It Is expected to retrieve the targetimage id from build id Additional info: [root@intel-d3c69-01 ~]# rpm -qa | grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch aeolus-configure-2.5.0-16.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch aeolus-all-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-11.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch