Answer by GLaupre for Hello guys, The instances are not started catching IP...
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:...
View ArticleComment by Carlos Alberto for When I reboot my neutron node I always have the...
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...
View ArticleAnswer by Mathias Ewald for Hello guys, The instances are not started...
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 :)
View ArticleComment by dheeru for Hello guys, The instances are not started catching IP...
can you paste ovs-vsctl show and ovs-vsctl list Interface . You can put this in paste.openstack.org
View ArticleComment by Carlos Alberto for Hello guys, The instances are not started...
sorry for the delay http://paste.openstack.org/show/73457/
View ArticleComment by dheeru for Hello guys, The instances are not started catching IP...
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...
View ArticleComment by Carlos Alberto for Hello guys, The instances are not started...
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!
View ArticleGrizzly - Instances not get DHCP IP
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...
View Article
