cloudpipe instance gets wrong IP
Bug #809316 reported by
Alexander Sakhnov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
While attempting to launch cloudpipe instance via 'nova-manage vpn run' command, its comes up with IP from 'common' instances DHCP pool and not the second IP from the subnet, which break the forwarding rules that allow users to access the vpn.
This is due 'allocate_fixed_ip' method in VlanManager doesn't get 'vpn' as an argument and cloudpipe instances always considers as 'common' instances.
Related branches
lp:~mirantis/nova/lp809316
- Mandell (community): Approve (community)
- Trey Morris (community): Approve
- Jason Kölker (community): Approve
- Matt Dietz (community): Approve
-
Diff: 72 lines (+9/-4)2 files modifiedAuthors (+1/-0)
nova/network/manager.py (+8/-4)
| Changed in nova: | |
| status: | New → Fix Committed |
| Changed in nova: | |
| milestone: | none → diablo-3 |
| Changed in nova: | |
| milestone: | diablo-3 → 2011.3 |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
