nova booted with neutron fails to obtain dhcp lease
Bug #1444219 reported by
Steven Dake
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kolla |
Fix Released
|
Critical
|
Steven Dake |
Bug Description
Console log:
http://
Script I ran to configure:
http://
Note I had to apply two patches:
https:/
https:/
Neutron works pretty well, can create ports etc was able to associate a floating ip with the machine, its just that its network interface doesn't come up, so the float doesn't work.
Changed in kolla: | |
status: | New → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Daneyon Hansen (danehans) |
no longer affects: | kolla/milestone-4 |
Changed in kolla: | |
milestone: | none → liberty-1 |
Changed in kolla: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Steve,
Thanks for the information. I believe we are experiencing the same issue. As you can see in your console log, the instance is not getting an IP from the dhcp agent and therefore can not reach metadata, work with a floating ip, etc.. Here is what you can do to work around the issue:
1. Stop and remove your neutron server and agents containers.
2. Drop the neutron DB in your mariadbapp container.
3. Start the neutron-server container. Look at the container logs and you should see that the DB gets recreated.
4. Make sure neutron-server is running by issuing a neutron ext-list and you should see a list of extensions loaded.
5. Start the agents container. Look at the logs and you should see all the agents connect to amqp.
6. The agents container is functioning when you can do a neutron agent-list and see a :-) next to each agent.
Now go ahead and run your neutron setup script. When the VM is active, view the console log and you should see that it obtains an IP from DHCP and successfully pulls metadata.
Everything is great until you stop and restart your agents container. When the container is restarted, the agents can no longer access the network namespaces that were created. We need to figure out why the namespaces are no longer available to the container after the restart.