RHV 4.4 upgrade considerations and known issues
Previous version RHV 4.3 upgrade considerations and known issues
Official Documentation
This content is not included.Upgrade Helper tool
Important: Always update your RHVM to latest z-stream available before moving to the next version. What happens if you don't.
Important: Lock ansible version before upgrading as per https://access.redhat.com/solutions/5480561.
Why to Upgrade? https://access.redhat.com/articles/6379751
RHV 4.4.9 requires new repositories: Manager / Hosts should be updated automaitcally, if upgraded via the Manager
1. Upgrading RHV hosts to RHV4.4 with kickstart files KCS
There has been a kickstart/anaconda bug in RHEL 8.2 that renders ignoredisks --drives directive in kickstart files unreliable.
2. RHV 4.4 will not support software FCoE.
Do not upgrade to RHV 4.4 in case you are using Software FCoE.
3. On HE setup, documentation needs to say that first of all Global Maintenance is required. Check This content is not included.bz#1866788 Upgrade steps from 4.3 to 4.4 are missing for HE deployment .
5. Hosted Engine appliance upgrade to RHV 4.4 fails due to gssapi packages missing.
Applicable to customers that configured SSO on RHV 4.3 HE VM.
6. Specific to RHV 4.4 GA hosts and upgrade of those to next versions. There is a problem on the hosts that were deployed with RHV 4.4 GA and are using multipath on local disks. The host will get into emergency mode and won't boot after reboot or upgrade. Here is how to avoid this problem:
https://access.redhat.com/solutions/5428651.
7. Upgrade to RHEL8.3 hosts will require manual switching of the AV stream from 8.2 to 8.3, if host upgrade is performed manually:
RHV: How to manually upgrade RHEL 8 Host to 8.3.
This is only relevant to RHEL based hosts.
8. There is a specific version of servers with FC HBA ports that RHEL8.3 will fail to detect the FC lun. In this case, it is recommended to wait till the next RHEL8.3.z is out with the correct drivers. Details are in This content is not included.Bug 1889953 - Failed to detect FC lun in RHEL 8.3 and RHVH 4.4.3 anaconda GUI.
9. In case RHV 4.3 setup has required networks in addition to ovirtmgmt, during migration to RHV4.4, the Hosted Engine setup for HE VM will pause giving the opportunity to configure those networks on the host. If those networks are not configured, HE setup will fail.
The hosted-engine deploy (restore-from-file) fails if any non-management logical network is defined as a required in backup file.
10. If using custom HTTPS certificates on RHV 4.3, the certs might not be included in the engine-backup and the hosted-engine deploy (restore-from-file) on RHV 4.4 fails with error "Cannot authenticate user 'None@N/A': No valid profile found in credentials"
11. Since RHEL 8.3 and RHVH 4.4.3, the TSX instructions are disabled in certain Intel CPUs, causing that the upgraded host becomes non operational with a CPU compatibility error. Before upgrading, verify that the cluster CPU model has been updated to use the noTSX version, and that all VMs running with the TSX instructions are power cycled. See also: Upgrade strategy for clusters with TSX enabled.
12. RHV 4.4 is not compatible with RHEL 8.4 until RHV 4.4.6 release.
There is about 2 weeks gap between the scheduled release of RHEL 8.4 and RHV 4.4.6. RHV 4.4.6 is the RHV z-stream, that will officially support RHEL 8.4 for its hypervisors and the manager. This is why it is recommended for RHV customers to NOT upgrade to RHEL 8.4 the moment it GAs and wait until RHV 4.4.6 is announced.
KCS
13. Since RHV 4.4.6, the cluster compatibility level 4.6 was introduced which changes the UID of the PCI root device of VMs using the Q35 chipset. The Windows VMs rediscover all devices after this change, so it is advised to configure them with the pc-q35-rhel8.3.0 machine type before this update to avoid any reconfiguration in the guest OS. See KCS 6320951
14. When using Spice through spice-proxy in RHV 4.3, the required packages are not installed during the upgrade process to RHV 4.4. For details check KCS 6956201
15. Windows Virtual Machines may have Virtual NICs and Disks losing configuration and/or going offline when the Cluster Level is changed as part of the upgrade. See KCS 6179481
16. Virtual Machine live migration is broken between RHV 4.4.z Service Pack 1 batch#1 and RHV 4.4.z Service Pack 1 batch#2 or, in a RHEL Advanced Virtualization deployment, kernel release below or equal to 4.18.0-372.16.1 and 4.18.0-372.26.1 or upper. See KCS 7030948
17. Live migration fails on those Virtual Machines which machine type is i440FX. See KCS 7053750.