After ml2/ovs to ml2/networking-ovn migration neutron resources are left on the database
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
networking-ovn |
Fix Released
|
Undecided
|
Miguel Angel Ajo |
Bug Description
Description of problem:
After ovn migration completed I check the output of OpenStack network agent list
and it looks like we can see the legacy neutron agent. They are not alive but still, I expected that they will not display in OVN deployment after migration process performed.
Ansible [migration: Deleting the neutron agents] actually ran in the controller-0. it is expected to be run in localhost (i.e undercloud)
TASK [migration : Generate neutron resources cleanup script] *******
task path: /home/stack/
Monday 19 November 2018 11:17:31 -0500 (0:00:00.586) 1:06:27.269 *******
META: noop
META: noop
META: noop
META: noop
changed: [controller-0] => {"changed": true, "checksum": "fd0d852ef79dfb
TASK [migration : Deleting the neutron agents] *******
task path: /home/stack/
Monday 19 November 2018 11:17:32 -0500 (0:00:01.061) 1:06:28.330 *******
META: noop
META: noop
META: noop
META: noop
changed: [controller-0] => {"changed": true, "cmd": "/home/
META: ran handlers
META: ran handlers
Changed in networking-ovn: | |
assignee: | nobody → Miguel Angel Ajo (mangelajo) |
status: | New → In Progress |
tags: | added: networking-ovn-proactive-backport-potential |
tags: | removed: networking-ovn-proactive-backport-potential |
Fix proposed to branch: master /review. openstack. org/618983
Review: https:/