Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

HELP! vm not accepting IP

Hi Guys,

Keep having this intermittent issue, need to figure it out please help. Every one in awhile an internal network will assign an ip and the VM no longer wants to accept it. Everything was working and then just stops. If i create a new network in smae project, new instances work fine. new instances on old network no longer work.

The VM boot log shows: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error. it also has no IP assigned to eth1

Neutron syslog is showing: dnsmasq-dhcp[8432]: message repeated 15 times: [ DHCPDISCOVER(tap66eeab4d-18) fa:16:3e:a5:9e:05 no address available]

I checked /var/lib/neutron/dhcp/network_id and all the info is correct (mac to IP) I also double checked all the services are running (metadata, dhcp-agent etc)

Have no idea where to go now..

HELP! vm not accepting IP

Hi Guys,

Keep having this intermittent issue, need to figure it out please help. Every one in awhile an internal network will assign an ip and the VM no longer wants to accept it. Everything was working and then just stops. If i create a new network in smae project, new instances work fine. new instances on old network no longer work.

The VM boot log shows: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error. it also has no IP assigned to eth1

Neutron syslog is showing: dnsmasq-dhcp[8432]: message repeated 15 times: [ DHCPDISCOVER(tap66eeab4d-18) fa:16:3e:a5:9e:05 no address available]

I checked /var/lib/neutron/dhcp/network_id and all the info is correct (mac to IP) I also double checked all the services are running (metadata, dhcp-agent etc)

Have no idea where to go now..

System running on ubuntu 14 openstack icehouse.

HELP! vm not accepting IP

Hi Guys,

Keep having this intermittent issue, need to figure it out please help. Every one in awhile an internal network will assign an ip and the VM no longer wants to accept it. Everything was working and then just stops. If i create a new network in smae project, new instances work fine. new instances on old network no longer work.

The VM boot log shows: url_helper.py[WARNING]: Calling 'http://169.254.169.254/2009-04-04/meta-data/instance-id' failed [0/120s]: request error. it also has no IP assigned to eth1

Neutron syslog is showing: dnsmasq-dhcp[8432]: message repeated 15 times: [ DHCPDISCOVER(tap66eeab4d-18) fa:16:3e:a5:9e:05 no address available]

I checked /var/lib/neutron/dhcp/network_id and all the info is correct (mac to IP) I also double checked all the services are running (metadata, dhcp-agent etc)

Have no idea where to go now..

System running on ubuntu 14 openstack icehouse.

UPDATE

So running tcpdump on DHCP interface on working instance shows request coming in. (sudo ip netns exec qdhcp-ff31bc90-dc60-4764-b660-8861170c1840 tcpdump -ln -i -v tap2dce5482-fa) .

Monitoring dump on non-working instance shows no request coming in.