Bug 1867458
| Summary: | [RHOSP 13 to 16.1 Upgrades][OvS Offload] Baremetal node hangs on reboot during leapp upgrade | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Saravanan KR <skramaja> |
| Component: | openstack-tripleo-heat-templates | Assignee: | Saravanan KR <skramaja> |
| Status: | CLOSED WONTFIX | QA Contact: | David Rosenfeld <drosenfe> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 16.1 (Train) | CC: | cfields, dmacpher, ealcaniz, fiezzi, hakhande, jamsmith, mburns |
| Target Milestone: | z1 | Keywords: | Triaged |
| Target Release: | 16.1 (Train on RHEL 8.2) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
A Leapp issue causes failure of fast forward upgrades from Red Hat OpenStack (RHOSP) platform 13 to RHOSP 16.1.
+
A Leapp upgrade from RHEL 7 to RHEL 8 removes all older RHOSP packages and performs an operating system upgrade and reboot. Because Leapp installs os-net-config package at the "overcloud upgrade run" stage, os-net-config-sriov executable is not available for sriov_config serivce to configure virtual functions (VF) and switchdev mode after reboot. As a result, VFs are not configured and switchdevmode is not applied on the physical function (PF) interfaces.
+
As a workaround, manually create the VFs, apply switchdevmode to the VF interface, and restart the VF interface.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-12-03 10:38:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Saravanan KR
2020-08-10 04:01:09 UTC
For nic paritionioning, the VFs will be used for an openstack network (InternalApi, Storage, Tenant). When the ifcfg scripts for the respective network is running, the underlying VF interface, will not be available. This will result in network.service failure. Also in order to restore the networks with VFs, os-net-config has to be run without "--no-activate". The same applies for offload feature as well, ifcfg run will expect the interface has been set to switchdev mode already, since sriov_config service didn't run, it will not be applied. network will be established in legacy mode and it requires to change the mode to switchdev, which also requires openvswitch to be restarted. Splitting this BZ in to 2 (1) OvS HW Offload - this BZ, it will be closed as WONT FIX, as we dont have active use case to suport it (2) Nic Partitioning - open a BZ to continue work on it The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |