Ask Your Question
0

Grizzly - Instances not get DHCP IP

asked 2014-02-19 08:17:51 -0500

Carlos Alberto gravatar image

updated 2014-03-02 18:53:38 -0500

Hello guys,

The instances are not started catching IP address automatically, I am basing the distribution documentation but have not found an exact solution.

This is an excerpt from the log:

udhcpc (v1.20.1) started

Sending discover...

Sending discover...

Sending discover...

No lease, failing

WARN: /etc/rc3.d/S40-network failed

cirros-ds 'net' up at 181.01

checking http://169.254.169.254/2009-04-04/instance-id (http://169.254.169.254/2009-04-04/ins...)

failed 1/20: up 181.03. request failed

failed 2/20: up 183.14. request failed

......( continues a few lines)

failed to read iid from metadata. tried 20

no results found for mode=net. up 221.34. searched: nocloud configdrive ec2

failed to get instance-id of datasource

=== network info ===

if-info: lo,up,127.0.0.1,8,::1

if-info: eth0,up,,8,fe80::f816:3eff:fe60:a7c3

edit retag flag offensive close merge delete

Comments

Are you using the GRE ? First check whether DHCP process is running on the netowork node (ps -aef | grep dhcp' ). If running can you check the where the packets are getting dropped ? May be sending ifconfig, your configuration etc

dheeru gravatar imagedheeru ( 2014-03-02 23:06:33 -0500 )edit

I'm using GRE, and DHCP processes running correctly. I'm watching my interfaces are always low (br-tun, br-int, tap ******** - **). got to see this in its structure? Thank you!

Carlos Alberto gravatar imageCarlos Alberto ( 2014-03-05 13:19:30 -0500 )edit

can you paste ovs-vsctl show and ovs-vsctl list Interface <gren>. You can put this in paste.openstack.org

dheeru gravatar imagedheeru ( 2014-03-05 22:30:55 -0500 )edit

sorry for the delay http://paste.openstack.org/show/73457/%3C/p%3E (http://paste.openstack.org/show/73457/)

Carlos Alberto gravatar imageCarlos Alberto ( 2014-03-13 15:53:51 -0500 )edit

2 answers

Sort by ยป oldest newest most voted
1

answered 2014-03-03 14:20:36 -0500

Mathias Ewald gravatar image

When I reboot my neutron node I always have the same problem. Turns out an interface (cannot remember which) is always down. Just and it and "ip link set dev DEV up" it :)

edit flag offensive delete link more

Comments

I watched my interfaces are always low (br-tun, en-int, tap ******** - **). but I'm using the Quantum. I heard a lot about dnsmasq, which according to the troubleshooting OpenStack, is responsible for assigning IP's for VM's Thank you!

Carlos Alberto gravatar imageCarlos Alberto ( 2014-03-05 13:24:30 -0500 )edit
0

answered 2014-11-14 15:54:58 -0500

GLaupre gravatar image

updated 2014-11-14 15:55:37 -0500

How did you fix the problem? I have the same issue: My instance doesn't received an ip:

udhcpc (v1.20.1) started
Sending discover...
Sending discover...
Sending discover...
No lease, failing
WARN: /etc/rc3.d/S40-network failed
Starting dropbear sshd: generating rsa key... generating dsa key... OK
no userdata for datasource

I am trying to solve this problem for days now. And as my instances don't get any IPs I can't access their console! Which is very annoying...

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower

Stats

Asked: 2014-02-19 08:17:51 -0500

Seen: 776 times

Last updated: Nov 14 '14