pcs enable/disable p_neutron-*-agent interrupts connectivity
Bug #1464817 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
High
|
Sergey Kolekonov |
Bug Description
Filing this as general issue.
Main problem with such behavior is lack of ability to restart agents without downtime.
For DHCP the issue is that it wastes DHCP port which never gets released. It also deletes agent from the database, which it should not. After the restart the agent gets another ip and have to create another dhcp port.
enable/disable of L3 or vpn agent causes loss of external connectivity.
Due to issues with ocf-script, ns-metadata-proxy processes are not getting killed and hence don't work after L3 process restart.
This should be fixed thoroughly in 7.0 and backported to all major releases: 6.1, 6.0, 5.1/5.1.1
Changed in fuel: | |
assignee: | nobody → MOS Neutron (mos-neutron) |
Changed in fuel: | |
milestone: | none → 7.0 |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in fuel: | |
assignee: | MOS Neutron (mos-neutron) → Ilya Shakhat (shakhat) |
Changed in fuel: | |
assignee: | Ilya Shakhat (shakhat) → Sergey Kolekonov (skolekonov) |
Changed in fuel: | |
status: | Confirmed → In Progress |
tags: |
added: release-notes-done-7.0 removed: release-notes |
tags: | added: on-verification |
tags: |
added: release-notes-done rn7.0 removed: release-notes-done-7.0 |
To post a comment you must log in.
Raised to High because DHCP/L3 agents downtime affects UX greatly