Bug 2011933 - [OVN migration] SR-IOV nodes are not fully migrated
Summary: [OVN migration] SR-IOV nodes are not fully migrated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 16.2 (Train)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 17.1
Assignee: Jakub Libosvar
QA Contact: Roman Safronov
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-10-07 18:58 UTC by Jakub Libosvar
Modified: 2023-09-04 20:24 UTC (History)
6 users (show)

Fixed In Version: openstack-neutron-18.6.1-1.20230518200966.el9ost
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-16 01:10:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-10271 0 None None None 2021-11-15 12:38:13 UTC
Red Hat Product Errata RHEA-2023:4577 0 None None None 2023-08-16 01:11:32 UTC

Description Jakub Libosvar 2021-10-07 18:58:32 UTC
Description of problem:
When migrating sr-iov nodes that don't have OVS agent running the migration steps fail and will not continue with migration tasks on the sriov nodes. This will lead to situation where nodes are left in inconsistent state with uncompleted migration.

Version-Release number of selected component (if applicable):


How reproducible:
100%

Steps to Reproduce:
1. Run OVN migration with SR-IOV nodes
2.
3.

Actual results:
Migration itself passes but sr-iov nodes are not migrated and have some leftovers.

Expected results:
sr-iov nodes have no leftovers

Additional info:
Perhaps sriov nodes don't need to run any steps during the migration.

br-migration is present on sr-iov nodes
OVN was not activated

TASK [stop-agents : stop and disable ovs services and healthchecks] **************************************************************************************************************
task path: /home/stack/ovn_migration/playbooks/roles/stop-agents/tasks/cleanup.yml:2
Wednesday 06 October 2021  18:19:17 +0000 (0:00:00.648)       0:00:08.091 *****
META: noop
META: noop
META: noop
failed: [computesriov-0] (item=tripleo_neutron_ovs_agent_healthcheck.timer) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent_healthcheck.timer
", "msg": "Could not find the requested service tripleo_neutron_ovs_agent_healthcheck.timer: host"}
failed: [computesriov-1] (item=tripleo_neutron_ovs_agent_healthcheck.timer) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent_healthcheck.timer
", "msg": "Could not find the requested service tripleo_neutron_ovs_agent_healthcheck.timer: host"}
failed: [computesriov-0] (item=tripleo_neutron_ovs_agent_healthcheck.service) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent_healthcheck.ser
vice", "msg": "Could not find the requested service tripleo_neutron_ovs_agent_healthcheck.service: host"}
failed: [computesriov-1] (item=tripleo_neutron_ovs_agent_healthcheck.service) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent_healthcheck.ser
vice", "msg": "Could not find the requested service tripleo_neutron_ovs_agent_healthcheck.service: host"}
failed: [computesriov-0] (item=tripleo_neutron_ovs_agent.service) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent.service", "msg": "Service i
s in unknown state", "status": {}}
failed: [computesriov-1] (item=tripleo_neutron_ovs_agent.service) => {"ansible_loop_var": "item", "changed": false, "item": "tripleo_neutron_ovs_agent.service", "msg": "Service i
s in unknown state", "status": {}}

Comment 8 Roman Safronov 2023-06-13 10:58:40 UTC
Verified that the issue does not happen on RHOS-17.1-RHEL-9-20230607.n.2 with openstack-neutron-ovn-migration-tool-18.6.1-1.20230518200966.el9ost.noarch

Comment 17 errata-xmlrpc 2023-08-16 01:10:52 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Release of components for Red Hat OpenStack Platform 17.1 (Wallaby)), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2023:4577


Note You need to log in before you can comment on or make changes to this bug.