Cannot boot instances under use_ipv6=true and with FlatManager/FlatDHCPManager
Bug #705811 reported by
Koji Iida
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
NTT PF Lab. | ||
Bexar |
Invalid
|
High
|
NTT PF Lab. |
Bug Description
With FlatManager/
Because nova-network doesn't set up IPv6 feature properly.
We are fixing this problem.
Workaround: please set use_ipv6 flag to false. (default is false after revision 579)
Related branches
lp:~ntt-pf-lab/nova/lp703037
- Soren Hansen (community): Approve
- Vish Ishaya (community): Approve
- Wayne A. Walls: Pending requested
-
Diff: 247 lines (+56/-32)8 files modifiedbin/nova-manage (+2/-2)
nova/network/linux_net.py (+5/-6)
nova/network/manager.py (+5/-1)
nova/test.py (+2/-1)
nova/tests/test_virt.py (+13/-0)
nova/utils.py (+6/-10)
nova/virt/libvirt.xml.template (+4/-2)
nova/virt/libvirt_conn.py (+19/-10)
Changed in nova: | |
assignee: | nobody → NTT PF Lab. (ntt-pf-lab) |
Changed in nova: | |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → Medium |
Changed in nova: | |
importance: | Medium → High |
Changed in nova: | |
milestone: | bexar-gamma → 2011.1 |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
We fixed boot the problem of FlatDHCPManager.
However, we would like to postpone to support ipv6 in FlatManager until Cactus release.
Because our current ipv6 implementation is based on the RA Server, however FlatManager don't use the RA Server.
So, the fixation needs many changes in current code.