Red Hat Virtualization Upgrade Helper

Updated -

This app is designed to help you upgrade your RHV to a newer version. All you need to provide is information about your upgrade path. We will not only present you the steps to upgrade RHV, but we'll also give you some extra steps that will prevent known issues specific to your upgrade scenario.
It supports the following upgrade paths:

  • 3.0 to 3.1
  • 3.1 to 3.2
  • 3.2 to 3.3
  • 3.3 to 3.4
  • 3.4 to 3.5
  • 3.5 to 3.6
  • 3.6 to 4.0
  • 4.0 to 4.1

Was this helpful?

We appreciate your feedback. Leave a comment if you would like to provide more detail.
It looks like we have some work to do. Leave a comment to let us know how we could improve.
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Get notified when this content is updated

Follow

7 Comments

Subscriber exclusive content

An active Red Hat subscription is required to participate.

Log In

will be helpful if upgrade path is specified like if RHEV-H has to be upgraded first and then RHEV-M etc

Hi sathyamoorthy,

Thanks for the suggestion. We will add it.

Thanks,
Dong

Great help and make things a lot of easier.

However, something which is not clear (we don't have knowledge of Jboss). The last step is:

Step 5 : Update JBoss Application Server

But what todo after this step. Do we need to restart processes or something OR is this really it? :-)

Hello Gerwin,

Step 5 is yum update whcih will upgrade the JBOSS application server.
This usually does not require reloading ovirt-engine service if you do not wish to disrupt
the end users. However it's recommended to perform "service ovirt-engine restart" at some point
in order to make sure you're using the latest JBossAS binaries for loading engine/reports.

Kind regards

Tomas Dosek
Senior Software Maintenance Engineer - Virtualization

P.S. We're already working on reflecting your feedback in the tool.
It's much appreciated one, thanks for it.

Terminal (command line) instructions are too light to make out. Can the font or background be changed to something more visually appealing?

Hi Jaime, thanks for reporting this issue. There seems to be something wrong with the app's stylesheet. We are not fixing it.

Dong Zhao

Jaime,

This problem has been fixed. Thanks for your patience.

Thanks,
Dong

I don't see any mention of the steps required to upgrade DWH and reports.

It would be helpful to add big important warning from official documentation, "Always update to the latest minor version of your current Red Hat Enterprise Virtualization Manager version before you upgrade to the next major version.". https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.4/html/Installation_Guide/sect-Upgrading_to_Red_Hat_Enterprise_Virtualization_3.4.html

For upgrade (such as from RHEV 3.3 to 3.4), please may I suggest to insert, after Step 3 (# engine-setup) and before Step 4 (# rhn-channel --remove...), the following steps...

      # yum install rhevm-dwh-setup rhevm-reports-setup
      # engine-setup

It is quite confusing that the upgrade helper does not mention anything regarding to the DWH and Reports upgrade.

And by the way, it seems that Step 3 fails as it cannot start ovirt-engine-dwhd service. And it only resolves when DWH and Reports are upgraded and "engine-setup" is ran again.

Mathew,
Thank you very much for the suggestion. We will add it.

Best regards,
Yunfeng

Hey,

When going through the upgrade path from 3.4 to 3.5, if you select that you are going to use RHEL 7-based Hypervisors, the following link is given as a preparation:

RHEL 7 hypervisors configured with DHCP are losing network connectivity, please follow the KCS to avoid it.
https://access.redhat.com/solutions/1241543

This is the same link as the preparation steps regarding yum failing when upgrading RHEL 6.5 hypervisors to 6.6:

Yum update fails when attempting to update RHEL Hypervisor to RHEL 6.6, please follow the KCS to avoid it.
https://access.redhat.com/solutions/1241543

I believe the correct link for the RHEL 7-based hypervisors preparation steps is:

https://access.redhat.com/solutions/1345623

Regards

Facundo,
Thank you very much.
We will fix it soon.

Regards

On the Step 1 , the link show the text "https://access.redhat.com/solutions/398993" but the link points to "https://access.redhat.com/labs/rhevupgradehelper/r.kcs" which show no information.

Hi Pablo,
Thank you for reporting this issue.
We have fixed it.
Thanks again.

Yunfeng Zhao

As Mathew Tse mentioned earlier

==================================================== For upgrade (such as from RHEV 3.3 to 3.4), please may I suggest to insert, after Step 3 (# engine-setup) and before Step 4 (# rhn-channel --remove...), the following steps...

  # yum install rhevm-dwh-setup rhevm-reports-setup
  # engine-setup

It is quite confusing that the upgrade helper does not mention anything regarding to the DWH and Reports upgrade.

And by the way, it seems that Step 3 fails as it cannot start ovirt-engine-dwhd service. And it only resolves when DWH and Reports are upgraded and "engine-setup" is ran again.

March 4 2015 at 12:41 AM

The step 3 is:

# yum update rhevm-dwh rhevm-reports

which is wrong, as it fails due to dependencies. Engine setup is handling the setup of dwh/reports and needs the newer setup files.

Alex, Thank you very much. We have fixed it.

Hello Zhao,

Thanks for editing the Upgrade Helper, although there is still a mistake.

The "# yum update rhevm-reports rhevm-dwh" should be removed completely.

We want:

# yum update rhevm-setup
# yum install rhevm-reports-setup rhevm-dwh-setup
# engine-setup

Nothing else between them.

Thank you again, Alexandros

Thanks, Alex. We have fixed it.

Seems perfect. Thank you once more.

3.5 -> 3.6 Step 3 is obsolete. When running # yum update rhevm-setup it updates also the dwh/reports-setup packages.

I can provide the output if needed

What if I also want to move from standalone engine to hosted? That's not a covered use case. Also, since storage domains are supposed to be importable now, is it not an easier route to simply deploy a new setup, and import the domains from the old one, instead of dragging the database back and forth? DWH will be lost, but for me it isn't critical

Hello Alexey,

Thank you for bringing up these questions. I am not behind the development of this tool, but as i understand this is solely meant to help with Upgrading and not Migrating (eg. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.6/html/Self-Hosted_Engine_Guide/chap-Migrating_from_Bare_Metal_to_a_RHEL-Based_Self-Hosted_Environment.html )

Also on your second question: The user would have to add again all the Hosts, configure all the Networking and the rest of the settings and configuration. The Import functionality is used mainly to move Storage Domains between environments or for Disaster Recovery scenarios.

We updated from 3.5 to 3.6 but did not had 3.5 cluster compatibility level yet. Because of did we encountered the problem: "no cpu profile". The cause/fix is located on in https://access.redhat.com/solutions/2695421 . Would love to knew this issue before we did the initial upgrade. Maybe an idea to add an extra question about it.

BTW for the rest I love this tool :-)

Hello Gerwin,

Thank you a lot for bringing this to our attention. As i see the KCS solution was written recently. I will make sure that the RHEV Upgrade Helper will be updated accordingly.

We are glad that you find this Helper useful.

In the 3.6 to 4.0 procedure the app has this questions:

"What is vdsm version on your hosts? Is it before RHEL 6: vdsm-4.16.37-1 or RHEL 7: vdsm-4.17.31-0?"

This question is confusing because the question only can be answered with yes or no. Can this be clarified?

  • Gerwin

Hello,

I'm trying to check the path for migration from 3.5 to 3.6, and at the question "Did you install the rhevm-dwh package?" and select "Yes" points me to:

' Why does RHEV-M 3.6 uprade failes with error "dwhd is currently running" ? https://access.redhat.com/solutions/2207531 '

When i go to that links says me "Access denied", how can i do to access this article to tackle that issue?

Hi Pablo, After confirmed with senior engineer, the issue is still affecting the upgrade from RHEV 3.5. The solution is back online. You can access the solution now. Thanks.