Is it necessary to update RHEL Hypervisor regularly

Latest response

We are using rhev-m 3.7 and RHEV 7.3. Should we update RHEV-M and RHEV (RHEL Hypervisor) regularly.

If required please suggest roll back procedure.

Responses

Hi Sandipan,

I would advise to update regularly. About a rollback procedure I would advise you to open a support case. RHEV-M 3.x is replaced by RHV 4.y.

As I do not use these products I cannot tell you whether or not you might get issues trying to update from RHEV-M 3.7 to RHV 4.2

Updating from RHEL 7.3 to RHEL 7.6 is supported by Red Hat.

Regards,

Jan Gerrit Kootstra

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html/upgrade_guide/

tells you how you need to upgrade RHEV-M to RHV-M.

It needs to be done in a couple of steps.

A direct upgrade is not supported.

Hi Sandipan,

Some add-on info.....

This may help you in case you are planning to upgrade https://access.redhat.com/labsinfo/rhvupgradehelper

This link would help to view details on life cycle of RHV https://access.redhat.com/support/policy/updates/rhev

Yes, you should update the manager and hypervisor images regularly.

As the product lifecycle page shows, RHV has a shorter lifecycle than some other products (such as RHEL) so if you leave a RHV installation then it risks becoming unsupported, as your 3.x installation already is. Even the extended support for RHV 3 ended in Sept 2018.

The lifecycle page also explains the expectation that you should update to each minor version:

"Although the cumulative life-cycle of a RHV release is 60 months, customers are expected to update to new minor and z-stream releases as and when they become available."

There is no upgrade path directly to 4.2, you will need to update to 4.0 then 4.1 then 4.2 to get the lastest version. Strong recommendation to perform this as soon as you can.

I believe we will still assist with upgrading the last old minor release to the current supported release if required. We always want our customers to be in a supported situation.

Generally there is not a rollback path. The upgrades are designed and tested to be reliable, but of course do perform a backup of the manager database before you start. In the rare case where an upgrade fails, we usually try to get the environment working on the upgrade target version. You can migrate guests off a hypervisor, update that hypervisor, then move guests on to the new hypervisor and upgrade other hypervisors.

Hi Sandipan,

Are you running RHEV-M 3.7 or RHEV-M 3.6?

I ask this, because I opened a support case due to an error in the upgrade manual and the Red Hat support engineer told me there is no RHEV-M 3.7.

Regards,

Jan Gerrit Kootstra

Hello,

There is no RHEV-M 3.7 , the latest version in RHEV 3.x is RHEV 3.6 version.

Refer: https://access.redhat.com/support/policy/updates/rhev

RHEV 3.x version is end of life.

The environment should be upgraded to RHV 4.x version.

Red Hat Technical Support recommends to open a proactive active for upgrading the RHV environment.