Bug 1956787 - 13->16 FFU: neutron agents are not upgraded to 16 on compute nodes as part of hybrid state.
Summary: 13->16 FFU: neutron agents are not upgraded to 16 on compute nodes as part of...
Status: NEW
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 16.2 (Train)
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact: Eran Kuris
Depends On:
TreeView+ depends on / blocked
Reported: 2021-05-04 12:15 UTC by smooney
Modified: 2021-05-17 13:45 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed:
Target Upstream Version:

Attachments (Terms of Use)

Description smooney 2021-05-04 12:15:11 UTC
Description of problem:
During an FFU form 13 to 16 the compute nodes are upgraded to the hybrid state
where the 16 version of all container bar nova_libvirt are intended to be  deployed on the rhel 7 host.

This is done to allow move operations(live migration) to be performed on the vms on that host prior to the leapp upgrade form rhel 7 to rhel8

During the FFU the nuetorn agent on the compute node are not also moved to the osp 16 version.

as a result it is unsafe to execute move operations as we cannot role back any failures.

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

How reproducible:
100%? this was observed in a customer session but shoudl affect all upgrades?

Steps to Reproduce:
1. deploy osp 13 with ml2/ovs
2. Follow FFU procedure to hybrid state
3. check version of neutron containers on a hybrid state compute node.

Actual results:
osp 13 version of neutron containers are present.

Expected results:

osp 16 version of neutron containers are deployed.

Additional info:

The OSP 13 version of the neutron l2 agent do not support multiple port binding
which means if an error occurse with a live migration we cannot role back.
in general it is also unsafe to mix osp 13 agents with osp 16 contolplane services as this combination is untested and unsupported.

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