Scheduling router without external network results in unclear error
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Won't Fix
|
Low
|
Unassigned |
Bug Description
When attempting to schedule a router to an L3 agent without an external network set, the following error is observed:
root@infra01_
Agent 7ec8336e-
The error could lead users to believe the L3 agent(s) are not alive when the agent-list clearly shows otherwise:
root@infra01_
| 7ec8336e-
| b5d7be19-
| e8bed137-
The test case in get_l3_
The proper workflow appears to be that a gateway must be set before a router can be scheduled. However, already scheduled routers can have their gateway cleared with no observed issues and remain scheduled.
It may help to create a new error to represent this failed test case rather than lumping tests together, or provide additional pointers in the error message to reflect possible issues other than a disabled or non-L3 agent.
Changed in neutron: | |
status: | New → Triaged |
importance: | Undecided → Low |
tags: | added: low-hanging-fruit |
Changed in neutron: | |
assignee: | nobody → Jin Li (jl7351) |
Changed in neutron: | |
assignee: | Jin Li (jl7351) → nobody |
Changed in neutron: | |
assignee: | nobody → Trevor McCasland (twm2016) |
Changed in neutron: | |
assignee: | Trevor McCasland (twm2016) → nobody |
status: | In Progress → Opinion |
Fix proposed to branch: master /review. openstack. org/311208
Review: https:/