The following points have been raised by engineering and must be incorporated into documentation - 1) In upgrading to 3.4 we need to tell users that they need to install upgrade packages prior to 3.3 upgrade for complete upgrade. This needs to be in the same location where we tell them to update 'rhevm-setup'. something like; If you have DWH and\or reports also run: # yum install rhevm-reports-setup # yum install rhevm-dwh-setup Then: # engine-setup 2) in updating DWH & reports. We need to remove the section about separate updating. This is not needed anymore, since otopi will update the packages for the user.
Fixed in 30126.
Documentation Link ------------------------------ https://documentation-devel.engineering.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtualization/3.5-Beta/html-single/Administration_Guide/index.html#Upgrading_to_Red_Hat_Enterprise_Virtualization_Manager_3.4 What Changed ------------------------------ The following topic was revised to add a new step - Step 3. - for updating the Reports and DWH features. While this topic covers the upgrade and not the installation, this was verified as the correct behavior as of the time the bug was written. Upgrading to Red Hat Enterprise Virtualization Manager 3.4 [30126-638215] Updated the revision history: [34613-686540] NVR ------------------------------ Red_Hat_Enterprise_Virtualization-Administration_Guide-3.5-Beta-en-US-3.5-5 Moving to ON_QA.
Peer reviewed. Step 3 is about updating Reports and DWH. No errors found. VERIFIED