Hide Forgot
Description of problem: using aeolus-image build creates a component outline in UI, but no providers are set to "building" recreate: [root@qeblade30 ~]# aeolus-image build --template audrey-client-RHEL6-vsphere.tpl --target vsphere Image Build Target Image Target Status ------------------------------------ ------------------------------------ ------------------------------------ ------- -------- 1cf98862-5977-412c-81c9-5bdba2104cd3 0a46bfe9-c559-4c0b-826c-e0ffa3018e1e 4100bc83-48bc-4301-a428-4f37ab7170e1 vsphere BUILDING 2. check factory log yup a build has been kicked.. <target dev="vda" bus="virtio"/> <source file="/var/lib/imagefactory/images/base-image-4100bc83-48bc-4301-a428-4f37ab7170e1.dsk"/> </disk> </devices> </domain> 2012-02-13 21:34:51,255 DEBUG oz.Guest.RHEL6Guest thread(4100bc83) Message: Waiting for factory-build-4100bc83-48bc-4301-a428-4f37ab7170e1 to finish installing, 3600/3600 2012-02-13 21 3. go to conductor/images/$image notice the vsphere provider is not set to building in the webui.. [root@qeblade30 ~]# rpm -qa | grep aeolus aeolus-conductor-daemons-0.8.0-25.el6.noarch rubygem-aeolus-image-0.3.0-7.el6.noarch aeolus-configure-2.5.0-12.el6.noarch aeolus-conductor-0.8.0-25.el6.noarch aeolus-conductor-doc-0.8.0-25.el6.noarch rubygem-aeolus-cli-0.3.0-8.el6.noarch aeolus-all-0.8.0-25.el6.noarch aeolus-audrey-agent-0.4.4-2.el6.noarch
*** Bug 796742 has been marked as a duplicate of this bug. ***
commit eaa850cd06730caea6039b80451b09066e6033cf Author: Martyn Taylor <mtaylor> Date: Wed Feb 29 14:51:56 2012 +0000 BZ#790250 Check Build Status on Show Image
7967c5d
Created attachment 566989 [details] UI shows building Kicked a build from cli for RHEV , UI shows building .. rpm -qa|grep aeolus aeolus-conductor-doc-0.8.0-39.el6.noarch rubygem-aeolus-cli-0.3.0-12.el6.noarch aeolus-all-0.8.0-39.el6.noarch aeolus-conductor-0.8.0-39.el6.noarch rubygem-aeolus-image-0.3.0-11.el6.noarch aeolus-configure-2.5.0-16.el6.noarch aeolus-conductor-daemons-0.8.0-39.el6.noarch
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