Bug 718231 - VMware instances do not report IP
Summary: VMware instances do not report IP
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: imagefactory
Version: 0.3.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
Assignee: Mike Orazi
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-01 14:12 UTC by Matt Wagner
Modified: 2014-08-17 22:27 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)
conductor gets ip from vsphere for RHEL 6 (221.19 KB, image/png)
2011-07-27 05:03 UTC, wes hayutin
no flags Details
err (200.90 KB, image/png)
2011-07-27 11:34 UTC, Shveta
no flags Details

Description Matt Wagner 2011-07-01 14:12:23 UTC
Description of problem:
When I build and push an image to vSphere, the guest that gets launched has no way of reporting an IP address. (Conductor gets a MAC address instead of an IP.) My understanding is that this is caused by the need to install the vmware guest tools.

Version-Release number of selected component (if applicable):
imagefactory-0.2.2-1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Build and push a Linux guest for the 'vmware' provider type.
2. Launch in Conductor. (Admittedly not terribly straight-forward at the moment.)
  
Actual results:
Instance returns a MAC address instead of an IP address. (If I find the guest in vSphere and access the console, it has obtained a valid IP.)

Expected results:
Instance reports its IP address.

Comment 1 Dave Johnson 2011-07-27 03:33:58 UTC
Want to do some more testing on this in the morning but this appears to be addressed with the latest rpms from brew

[root@ibm-ls21-03 aeolus-conductor]# rpm -qa | egrep 'aeolus|factory|delta'
aeolus-conductor-daemons-0.3.0-3.el6.noarch
rubygem-imagefactory-console-0.4.0-1.el6.noarch
imagefactory-0.4.1-1.el6.noarch
rubygem-deltacloud-client-0.3.1-1.el6.noarch
rubygem-deltacloud-client-doc-0.3.1-1.el6.noarch
libdeltacloud-0.9-1.el6.x86_64
rubygem-aeolus-image-0.0.1-3.el6.noarch
aeolus-all-0.3.0-2.el6.noarch
aeolus-conductor-0.3.0-3.el6.noarch
aeolus-configure-2.0.1-2.el6.noarch
deltacloud-core-0.3.9999-1308927004.2.el6.noarch
aeolus-conductor-doc-0.3.0-3.el6.noarch
condor-deltacloud-gahp-7.6.0-5dcloud.el6.x86_64

Comment 2 wes hayutin 2011-07-27 05:03:57 UTC
Created attachment 515412 [details]
conductor gets ip from vsphere for RHEL 6

leaving in on-qa because of Dave's above comment.. but here are my results...

[root@intel-d3c4702-01 ~]# rpm -qa | grep aeolus
aeolus-configure-2.0.1-2.el6.noarch
aeolus-conductor-0.3.0-3.el6.noarch
aeolus-conductor-daemons-0.3.0-3.el6.noarch
rubygem-aeolus-image-0.0.1-3.el6.noarch
aeolus-all-0.3.0-2.el6.noarch
aeolus-conductor-doc-0.3.0-3.el6.noarch
[root@intel-d3c4702-01 ~]# rpm -qa | grep imagefactory
rubygem-imagefactory-console-0.4.0-1.el6.noarch
imagefactory-0.4.1-1.el6.noarch
[root@intel-d3c4702-01 ~]# rpm -qa | grep iwhd
iwhd-0.97-1.el6.x86_64
[root@intel-d3c4702-01 ~]# 

whayutin@thinkdoe ~]$ ssh root.75.56
The authenticity of host '10.16.75.56 (10.16.75.56)' can't be established.
RSA key fingerprint is 31:b0:90:a4:79:0e:3d:45:1e:c1:f3:bd:52:fe:5c:b9.
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.16.75.56' (RSA) to the list of known hosts.
root.75.56's password: 
Last login: Wed Jul 27 01:00:19 2011
[root@dhcp75-56 ~]# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:50:56:A9:00:E2  
          inet addr:10.16.75.56  Bcast:10.16.75.255  Mask:255.255.252.0
          inet6 addr: fe80::250:56ff:fea9:e2/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:944 errors:0 dropped:0 overruns:0 frame:0
          TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:68138 (66.5 KiB)  TX bytes:9736 (9.5 KiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:6 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:298 (298.0 b)  TX bytes:298 (298.0 b)

[root@dhcp75-56 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux Server release 6.1 (Santiago)
[root@dhcp75-56 ~]#

Comment 3 Shveta 2011-07-27 11:19:41 UTC
Still getting MAC address .

Comment 4 Shveta 2011-07-27 11:34:07 UTC
Created attachment 515480 [details]
err

 rpm -qa|grep aeolus
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
aeolus-conductor-doc-0.3.0-3.el6.noarch
aeolus-conductor-0.3.0-3.el6.noarch
aeolus-configure-2.0.1-2.el6.noarch


[root@snowstorm ~]# rpm -qa | grep imagefactory
imagefactory-0.4.1-1.el6.noarch
rubygem-imagefactory-console-0.4.0-1.el6.noarch


rpm -qa | grep iwhd
iwhd-0.97-1.el6.x86_64

Comment 5 wes hayutin 2011-07-27 13:24:37 UTC
Shveta did you have the vmware tools installed on the client?

Comment 6 wes hayutin 2011-07-27 13:28:34 UTC
getting the ip address to be displayed in conductor using a RHEL6 vsphere instance worked for me.

I used the rhel6 vmware template here..
https://engineering.redhat.com/trac/IntegratedMgmtQE/wiki/cloudengine_buildingRHEL6

This bug was verified on the build listed in comment#2.  I think the issues has been fixed and this was moved to on_dev in error.  QE should recheck.

Comment 7 Dave Johnson 2011-07-27 16:07:24 UTC
This is good 2 go based on comment 1 and comment 2 as well as additional testing that I did this morning.  If Shveta's problems persist we can reopen this.

Comment 8 wes hayutin 2011-08-01 20:00:43 UTC
release pending...

Comment 9 wes hayutin 2011-08-01 20:00:48 UTC
release pending...

Comment 10 wes hayutin 2011-08-01 20:00:57 UTC
release pending.. 2

Comment 12 wes hayutin 2011-12-08 14:02:19 UTC
closing out old bugs

Comment 13 wes hayutin 2011-12-08 14:14:18 UTC
perm close


Note You need to log in before you can comment on or make changes to this bug.