Deal with NetworkAmbiguous error
Today if a tenant has more than a network visible to it and during boot it does not specify any network, the famous NetworkAmbiguous is returned. It would be nice if there was a way for Nova and Neutron to fall back on the adoption of a tenant-level 'default' network.
Blueprint information
- Status:
- Not started
- Approver:
- Matt Riedemann
- Priority:
- Undefined
- Drafter:
- Hongbin Lu
- Direction:
- Needs approval
- Assignee:
- hongbin liu
- Definition:
- Review
- Series goal:
- None
- Implementation:
-
Unknown
- Milestone target:
- None
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Choose default network on ambiguity
Deferring this to Stein since the nova spec isn't approved yet in Rocky and we're past the spec freeze. Need to ensure the neutron team dependencies are met before we move forward in nova. -- mriedem 20180619
From Hongbin on the spec: "Abandoned will restore it once i have a chance to work on it in the future."
I'm going to un-target this from Stein for now since the spec has been abandoned. We can re-target if the spec is re-proposed. -- melwitt 2018-10-24
