Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Build and pushed image foor RHEV 2. Created a deployable and launched isntance 3. It launched fine and started but in conductor UI it doesnt show IP and state is always Pending. Actual results: Expected results: Additional info:rpm -qa|grep aeolus aeolus-conductor-doc-0.3.0-2.el6.noarch aeolus-conductor-0.3.0-2.el6.noarch aeolus-configure-2.0.1-1.el6.noarch aeolus-all-0.3.0-2.el6.noarch rubygem-aeolus-image-0.0.1-3.el6.noarch aeolus-conductor-daemons-0.3.0-2.el6.noarch
FYI.. the IP addr for RHEV/RHEVM at this time will not work. That is a known issue. The fact it stays in pending.. is an issue. :)
I could not reproduce this, instances transitioned from pending to running in my test environment.
Created attachment 515644 [details] err Instance state shows running now and reports MAC address. rpm -qa |grep aeolus aeolus-conductor-0.3.0-3.el6.noarch aeolus-conductor-doc-0.3.0-3.el6.noarch aeolus-configure-2.0.1-2.el6.noarch aeolus-all-0.3.0-2.el6.noarch rubygem-aeolus-image-0.0.1-3.el6.noarch aeolus-conductor-daemons-0.3.0-3.el6.noarch
While RHEV instances are launched successfully they do not report an IP Address of the running instance even if the instance successfully receives an IP Address. This is due to limitations in the RHEV 2.2 API. IP addresses should be reported successfully in RHEV 3.0 API.
This bug is closed(fixed) for me.
Hey Francesco.. so we're just waiting for the patch to drop to the testing repo I take it? Do you by chance have the git hash w/ the fix?
Hey Wes there's no patch for this. Is a matter of RHEV 2.2 and 3.0 as james labocki said above. Since I run different istances and after a while they give me back the ip address without any problem with deltacloud. RHEV return the mac address at the beginning and after a while it return the ip, at least with RHEV 3, due to DHCP || config server. I am willing to work with shveta|wes|dan to sort the problem out again.
Dave, once you have a working rhevm3.0 env.. please give this a whirl. In fact you could probably snif this out w/o aeolus and just use deltacloud
making sure all the bugs are at the right version for future queries
I launched rhevm deployment and i see that IP assigned is the loop back address. ie :IP Address: 127.0.0.1:5890 see attached screenshot: <akarol> ie :IP Address: 127.0.0.1:5890 <akarol> Is this the correct one? <fvollero> akarol: This happen when guest tools are not installed on the template of rhev. Tbh, seems strange that i give u the loopback ip, but sadly, deltacloud act just as broker, so the informations that RHEV-m give, dc just return back. <fvollero> akarol: I can talk with rhev guys to understand if is something that they can fix. <mfojtik> fvollero, akarol: loopback is used for VNC/Spice connection <fvollero> mfojtik: you agree with what I said to akarol ? <fvollero> mfojtik: so my answer was right <mfojtik> fvollero, akarol: we're actually not supporting this type of connection (it requires to create a 'ticket' in RHEV-M) [root@dell-per905-01 templates]# rpm -qa | grep aeolus aeolus-all-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-conductor-doc-0.4.0-0.20111003184622git65a7d19.fc15.noarch rubygem-aeolus-image-0.1.0-3.20111003170706git8f23238.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111003133323git9451323.fc15.noarch aeolus-configure-2.0.2-4.20110930103205gitaf78594.fc15.noarch aeolus-conductor-daemons-0.4.0-0.20111003184622git65a7d19.fc15.noarch aeolus-conductor-0.4.0-0.20111003184622git65a7d19.fc15.noarch
Created attachment 526231 [details] rhevm ip
Deployment-juyob/testRHEVM IP Address:: hp-nehalem-02.rhts.eng.bos.redhat.com:5904 State:: running [root@qeblade31 nodes]# rpm -qa | grep deltacloud deltacloud-core-rhevm-0.4.1-3.fc15.noarch deltacloud-core-vsphere-0.4.1-3.fc15.noarch deltacloud-core-0.4.1-3.fc15.noarch deltacloud-core-ec2-0.4.1-3.fc15.noarch rubygem-deltacloud-client-0.4.0-3.fc15.noarch [root@qeblade31 nodes]# rpm -qa | grep aeolus aeolus-conductor-0.5.0-0.20111025005411git5ff5abd.fc15.noarch aeolus-configure-2.2.0-1.20111024205543gitf9232cc.fc15.noarch aeolus-conductor-daemons-0.5.0-0.20111025005411git5ff5abd.fc15.noarch rubygem-aeolus-cli-0.1.0-3.20111024205439gitc3aa990.fc15.noarch aeolus-all-0.5.0-0.20111025005411git5ff5abd.fc15.noarch rubygem-aeolus-image-0.1.0-4.20111024205454git6b2b696.fc15.noarch aeolus-conductor-doc-0.5.0-0.20111025005411git5ff5abd.fc15.noarch [root@qeblade31 nodes]#
http://post-office.corp.redhat.com/archives/rhev-beta/2011-October/thread.html#00419
Deployment-juyob/testRHEVM IP Address:: 10.16.71.209 State:: running
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