Tap interface does not automatically get an IP address upon a hypervisor reboot
Bug #1084355 reported by
Salman Baset
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Invalid
|
Medium
|
dan wendlandt |
Bug Description
A very simple configuration, in which there is a subnet and a net. No floating.
The tap interface gets an IP address when a subnet is created. For instance for 172.16.10.0/24 subnet, tap interface gets an IP address of 172.16.10.2
However, upon a reboot, tap interface does not always shows up, and does not automatically get an IP address. As a result, IP assignment to a new instance fails.
Changed in nova: | |
importance: | Undecided → High |
Changed in quantum: | |
milestone: | none → grizzly-rc1 |
summary: |
- Tap interface does not automatically get an IP address upon a reboot + Tap interface does not automatically get an IP address upon a hypervisor + reboot |
tags: | added: ovs |
To post a comment you must log in.
Hi,
Can you please clarify a few things:
1. Are you working from packages?
2. The tap interface that you are referring to is from the DHCP agent. Can you please check if this is running after reboot (please also check the log file)
Thanks
Gary