[rhos-list] Cirros VM image DHCP issues

[Rhys Oxenham]

On 26 Aug 2013, at 12:28, Perry Myers <pmyers at redhat.com> wrote:

> On 08/26/2013 07:14 AM, Prashanth Prahalad wrote:
>> Hi Folks,
>> 
>> I just wanted to bounce this on the alias and get ideas on what could be
>> going on. I've a quantum/OVS setup. I spin up the Cirros image and when
>> the machine comes up it fails to get the DHCP address. 
>> 
>> I do see the DHCP request and the DHCP reply coming back from the DHCP
>> server.
>> 
>> Here's the tcpdump on the tap interface attached to the VM:
>> 
>> [root at rhos3 ~]# *tcpdump -i tap97c9b343-4a*
>> tcpdump: WARNING: tap97c9b343-4a: no IPv4 address assigned
>> tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
>> listening on tap97c9b343-4a, link-type EN10MB (Ethernet), capture size
>> 65535 bytes
>> 04:09:47.852793 IP6 :: > ff02::16: HBH ICMP6, multicast listener report
>> v2, 1 group record(s), length 28
>> *04:09:47.857854 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>> Request from fa:16:3e:a6:eb:e6 (oui Unknown), length 280*
>> *04:09:47.857858 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>> Request from fa:16:3e:a6:eb:e6 (oui Unknown), length 280*
>> *04:09:47.858132 IP 192.168.10.3.bootps > 192.168.10.6.bootpc:
>> BOOTP/DHCP, Reply, length 322*
>> *04:09:47.858395 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>> Request from fa:16:3e:a6:eb:e6 (oui Unknown), length 292*
>> *04:09:47.858397 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP,
>> Request from fa:16:3e:a6:eb:e6 (oui Unknown), length 292*
>> *04:09:47.858493 IP 192.168.10.3.bootps > 192.168.10.6.bootpc:
>> BOOTP/DHCP, Reply, length 322*
>> 
>> [root at rhos3 ~]# *ifconfig tap97c9b343-4a*
>> tap97c9b343-4a Link encap:Ethernet  HWaddr FE:16:3E:A6:EB:E6  
>>          inet6 addr: fe80::fc16:3eff:fea6:ebe6/64 Scope:Link
>>          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>>          RX packets:74 errors:0 dropped:0 overruns:0 frame:0
>>          TX packets:10943 errors:0 dropped:0 overruns:0 carrier:0
>>          collisions:0 txqueuelen:500 
>>          RX bytes:18144 (17.7 KiB)  TX bytes:620606 (606.0 KiB)
>> 
>> 
>> So any ideas why this DHCP reply is being rejected by the Cirros VM ?
>> 
>> Any clue on how to debug this further.
> 
> What kernel are you running on the host?
> 
> There is a known issue with the kernel shipped with RHOS that would
> cause this behavior.  There is a fixed kernel available in RDO
> repositories right now
> (kernel-2.6.32-358.114.1.openstack.el6.gre.2.x86_64) but it is not yet
> available via RHOS 3.0 repos.  It should be available there in the next
> few weeks.

Hi Prashanth,

Are you using Cirros 0.3.0? It has a bug where it completely ignores DHCP responses. Before continuing debugging, please try 0.3.1 and let us know whether this fixes it…

wget http://download.cirros-cloud.net/0.3.1/cirros-0.3.1-x86_64-disk.img

Cheers
Rhys


> 
> Perry
> 
> _______________________________________________
> rhos-list mailing list
> rhos-list at redhat.com
> https://www.redhat.com/mailman/listinfo/rhos-list