failed to update an external network into non external network
Bug #1083387 reported by
yong sheng gong
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
yong sheng gong | ||
Folsom |
Fix Released
|
Medium
|
Gary Kotton | ||
quantum (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I have one external network and have a gateway port on it.
I create one more external network but regret (I often do that) and try to update it back into normal one:
quantum net-update testpub2 --router:external False
External network ea1f9c63-
Related branches
lp:~gandelman-a/ubuntu/quantal/quantum/2012.2.1
- Openstack Ubuntu Testers: Pending requested
-
Diff: 79 lines (+68/-0)1 file modifieddebian/changelog (+68/-0)
Changed in quantum: | |
importance: | Undecided → Medium |
assignee: | nobody → yong sheng gong (gongysh) |
milestone: | none → grizzly-2 |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in quantum (Ubuntu): | |
status: | New → Fix Released |
Changed in quantum (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
tags: | removed: in-stable-folsom |
Changed in quantum: | |
milestone: | grizzly-2 → 2013.1 |
To post a comment you must log in.
as far as I can tell, this is intended behavior, as otherwise you would have a router uplinked to a non-external network, which wouldn't make any sense. If you delete the router gateways that connect to this external network, you should then be able to change it back to an non-external net.