NSX: router_id_get should not raise an exception
Bug #1313918 reported by
Armando Migliaccio
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Armando Migliaccio | ||
Icehouse |
Fix Released
|
Medium
|
Armando Migliaccio |
Bug Description
During the migration of networks from the old agent-based model and the new agentless model networks router_id_get should not raise an exception; network's subnets may or may have not been uplinked to a router so it's perfectly acceptable to return None instead.
Changed in neutron: | |
assignee: | nobody → Armando Migliaccio (armando-migliaccio) |
Changed in neutron: | |
status: | New → In Progress |
Changed in neutron: | |
importance: | Undecided → Medium |
milestone: | none → juno-1 |
tags: | removed: icehouse-backport-potential in-stable-icehouse |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-1 → 2014.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/90824 /git.openstack. org/cgit/ openstack/ neutron/ commit/ ?id=5e843850527 ede7a56fcc24753 f87c1e9e3e8bed
Committed: https:/
Submitter: Jenkins
Branch: master
commit 5e843850527ede7 a56fcc24753f87c 1e9e3e8bed
Author: armando-migliaccio <email address hidden>
Date: Mon Apr 28 14:18:06 2014 -0700
NSX: do not raise on missing router during migration step
Return None for missing router rather raising NotFound exception;
this is what the client code was expected to handle in the first
place.
Closes-bug: 1313918
Change-Id: I573770a69d0170 b027fc990c29aaa 87b1fc8eccc