Bug 1548089

Description of problem:
Setup: 
Virt setup of OSP deployed with OSPD. ( deployment job) 


I created LB in public network. 
After creating listener pool and members  I tried curl request to the VIP. 

Response was " No route to host" 

As part of debugging, a VM was booted in the same public network. 

The console log showed the following: 
(overcloud) [stack@undercloud-0 ~]$ openstack console log show a9825ab3-08e4-4ed6-a5c8-9fcd57c4df65

.
.

Starting network...
udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
Usage: /sbin/cirros-dhcpc <up|down>
No lease, failing
WARN: /etc/rc3.d/S40-network failed
cirros-ds 'net' up at 184.71
checking http://169.254.169.254/2009-04-04/instance-id
failed 1/20: up 184.72. request failed
failed 2/20: up 186.77. request failed
failed 3/20: up 188.78. request failed
failed 4/20: up 190.79. request failed
failed 5/20: up 192.80. request failed
failed 6/20: up 194.81. request failed
failed 7/20: up 196.83. request failed
failed 8/20: up 198.84. request failed
failed 9/20: up 200.85. request failed
failed 10/20: up 202.86. request failed
failed 11/20: up 204.87. request failed
failed 12/20: up 206.88. request failed
failed 13/20: up 208.89. request failed
failed 14/20: up 210.90. request failed
failed 15/20: up 212.92. request failed
failed 16/20: up 214.93. request failed
failed 17/20: up 216.94. request failed
failed 18/20: up 218.95. request failed
failed 19/20: up 220.96. request failed
failed 20/20: up 222.97. request failed
failed to read iid from metadata. tried 20
no results found for mode=net. up 224.99. searched: nocloud configdrive ec2
failed to get instance-id of datasource
Top of dropbear init script
Starting dropbear sshd: failed to get instance-id of datasource
WARN: generating key of type ecdsa failed!
OK
=== system information ===
Platform: Red Hat OpenStack Compute
Container: none
Arch: x86_64
CPU(s): 1 @ 2200.002 MHz
Cores/Sockets/Threads: 1/1/1
Virt-type:
RAM Size: 113MB
Disks:
NAME MAJ:MIN     SIZE LABEL         MOUNTPOINT
vda  253:0   41126400
vda1 253:1   32901120 cirros-rootfs /
=== sshd host keys ===
.
.
.

=== network info ===
if-info: lo,up,127.0.0.1,8,::1
if-info: eth0,up,,8,fe80::f816:3eff:febd:f518
=== datasource: None None ===
=== cirros: current=0.3.5 uptime=225.24 ===
route: fscanf
=== pinging gateway failed, debugging connection ===
############ debug start ##############
### /etc/init.d/sshd start
Top of dropbear init script
Starting dropbear sshd: failed to get instance-id of datasource
WARN: generating key of type ecdsa failed!
FAIL
route: fscanf
### ifconfig -a
eth0      Link encap:Ethernet  HWaddr FA:16:3E:BD:F5:18
          inet6 addr: fe80::f816:3eff:febd:f518/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:273 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:11598 (11.3 KiB)  TX bytes:1132 (1.1 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:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)  

### route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
route: fscanf
### cat /etc/resolv.conf
cat: can't open '/etc/resolv.conf': No such file or directory
### gateway not found
/sbin/cirros-status: line 1: can't open /etc/resolv.conf: no such file
### pinging nameservers
### uname -a
Linux cirros 3.2.0-80-virtual #116-Ubuntu SMP Mon Mar 23 17:28:52 UTC 2015 x86_64 GNU/Linux



The VM is not receiving an address. 

We saw that the dhcp server in the subnet is false and updated the subnet with dhcp = true. 

It did not solve the issue. 

Cancelling the port security on the network did not assist as well. 

Version-Release number of selected component (if applicable):
13

How reproducible:
100%

Steps to Reproduce:
1.Create LB/VM in public network 
2. Try to reach the VM
3.

Actual results:
No IP assigned to the VM

Expected results:
Loadbalancing should work and the VM in the network should be reachable 

Additional info:

In devstack it works ok.