Unscheduling a router(HA/legacy) from an agent not scheduled for that router causes an error.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Yoni Shafrir |
Bug Description
A legacy router was created and automatically scheduled to both agents.
Given this state of the agent scheduling :
[stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-
+------
| id | host | admin_state_up | alive |
+------
| fda97b55-
+------
When trying to remove a router from the same agent twice an error occurs:
[stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-
Removed router R5 from L3 agent
[stack@vpn-6-98 devstack (master %=)]$ neutron l3-agent-
Conflict (HTTP 409) (Request-ID: req-9a96e8a2-
For reference, when trying to re-schedule the router on the same agent the client notifies the user:
neutron l3-agent-router-add fda97b55-
Added router R5 to L3 agent
neutron l3-agent-router-add fda97b55-
Added router R5 to L3 agent
There is no 'real' effect on the DB or anything but the client should indicate the operation failed
since the agent is already scheduled.
The second removal of the same agent shouldn't fail as we try to avoid
unnecessary errors.
Changed in neutron: | |
assignee: | nobody → Yoni (yshafrir) |
tags: | added: api l3-ipam-dhcp |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
summary: |
- Scheduling a router(HA/legacy) to an agent already scheduled for that - router yields a success message + Unscheduling a router(HA/legacy) from an agent not scheduled for that + router causes an error. |
description: | updated |
Changed in neutron: | |
milestone: | none → kilo-3 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-3 → 2015.1.0 |
Fix proposed to branch: master /review. openstack. org/148883
Review: https:/