RHV 4.3 upgrade considerations and known issues
-
RHV 4.0 is out of support in RHV 4.3. I.e. 4.0 Compatibility Level(CL) clusters and data centers are not supported in RHV 4.3. This requires a stepped upgrade via 4.2 CL first (Manager to 4.2 -> hosts to latest -> CL to 4.2 -> Manager to 4.3).
Upgrade Guide -
If on RHVM 4.0, hosts should not be updated until the Manager is upgraded to 4.2, otherwise hosts will get non-responsive until the manager is upgraded to 4.2 and CL of the cluster is updated to 4.2.
-
Due to JBoss EAP changes, manual changes of repositories are required during the upgrades between releases.
https://access.redhat.com/articles/4090791 -
Ovirt-fast-forward-upgrade tool is available to simplify this upgrade process. It provides a guided upgrade experience to latest RHV-M version available.
Upgrading with ovirt-fast-forward-upgrade -
RHV Upgrade Helper tool is regularly updated with any known issues in the upgrade process.
This content is not included.This content is not included.https://access.redhat.com/labs/rhvupgradehelper -
RHV 4.3 is not supported on Satellite 5.8.
https://access.redhat.com/node/4079341 -
RHV 4.2 EUS is available for x86 hypervisors, both RHEL based and RHVH.
What channels should be used for RHV 4.2 EUS -
If using third party CA for RHV-M, uploading images from the Admin Portal will require changes to ovirt-imageio-proxy.conf.
See details here -
Iptables has been deprecated.
Use firewalld -
Non-responsive DC and no SPM after upgrading DC CL to 4.3
https://access.redhat.com/solutions/4172251 -
If upgrading from RHEL7.5 hosts, the hosts would need to be reregistered to the manager at some point:
https://access.redhat.com/solutions/4731261