Bug 731490
Summary: | Need build completion notification outside of tailing imagefactory.log using CLI | ||
---|---|---|---|
Product: | [Retired] CloudForms Cloud Engine | Reporter: | William Henry <whenry> |
Component: | imagefactory | Assignee: | Imre Farkas <ifarkas> |
Status: | CLOSED ERRATA | QA Contact: | wes hayutin <whayutin> |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0.0 | CC: | akarol, athomas, dajohnso, deltacloud-maint, ssachdev |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-15 20:10:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
William Henry
2011-08-17 18:51:04 UTC
We're in the process in planning a build & push UI within the Conductor web app itself which will address this. making sure all the bugs are at the right version for future queries According to sseago, this issue has been resolved in the build/push UI in the latest Aeolus rev. Status examples: aeolus-cli status --targetimage $target_image # status of target image build aeolus-cli status --providerimage $provider_image # status of provider image push [root@qeblade31 conductor]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.7.0-4.fc16.noarch aeolus-all-0.7.0-4.fc16.noarch rubygem-aeolus-image-0.2.0-1.fc16.noarch aeolus-conductor-0.7.0-4.fc16.noarch rubygem-aeolus-cli-0.2.0-3.fc16.noarch aeolus-conductor-doc-0.7.0-4.fc16.noarch aeolus-configure-2.4.0-3.fc16.noarch [root@qeblade31 conductor]# [root@qeblade31 conductor]# aeolus-cli list --images ID Name OS OS Version Arch Description ------------------------------------ ------------------------------ ------ ---------- ------ ------------------------------------------------- 52bc7864-5c7b-420e-8774-ba1a936b84f2 RHEL6-Basic RHEL-6 1 x86_64 RHEL61 x86_64 ce03c517-8f51-4d85-94a8-72a92afa3cbf RHEL5-Basic RHEL-5 U7 x86_64 RHEL57 x86_64 36d71e79-d49d-4744-92ce-7453686a001a RHEL6-Basic RHEL-6 1 x86_64 RHEL61 x86_64 8ac49e19-55ca-454c-ae4e-a68678e6ac41 RHEL5-Basic RHEL-5 U7 x86_64 RHEL57 x86_64 7356dfd5-32b5-41d1-8e6c-9526f1ff6e82 RHEL6_VMWareTools RHEL-6 1 x86_64 RHEL61 x86_64 and VMWareTools cc5a3fe6-c684-40b3-b272-876fc996df99 rhel6_2_x86_64_with_rhev-agent RHEL-6 2 x86_64 rhel 6.2 x86_64 template with rhev v3.0 agent pkg [root@qeblade31 conductor]# aeolus-cli list --builds 52bc7864-5c7b-420e-8774-ba1a936b84f2 ID Image ------------------------------------ ------------------------------------ ccee82f8-35f8-469d-95c5-7aeb06dbc6aa 52bc7864-5c7b-420e-8774-ba1a936b84f2 [root@qeblade31 conductor]# aeolus-cli list --targetimages ccee82f8-35f8-469d-95c5-7aeb06dbc6aa ID Status Build ------------------------------------ -------- ------------------------------------ 291164a4-777f-4bcf-9591-66a2627f35d7 COMPLETE ccee82f8-35f8-469d-95c5-7aeb06dbc6aa [root@qeblade31 conductor]# aeolus-cli status --targetimage 291164a4-777f-4bcf-9591-66a2627f35d7 Build Status: COMPLETE [root@qeblade31 conductor]# aeolus-cli list --providerimages 291164a4-777f-4bcf-9591-66a2627f35d7 ID Target Identifier Provider Status Target Image ------------------------------------ ---------------------------------------------- -------- -------- ------------------------------------ f884f33c-fb11-4c1a-b9ce-92b8beec8858 Mock_mock_f884f33c-fb11-4c1a-b9ce-92b8beec8858 mock COMPLETE 291164a4-777f-4bcf-9591-66a2627f35d7 [root@qeblade31 conductor]# aeolus-cli status --providerimage f884f33c-fb11-4c1a-b9ce-92b8beec8858 Push Status: COMPLETE [root@qeblade31 conductor]# Appears that this is not updating in the UI as intended. Assigning to ifarkas per athomas's request. 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-0588.html |