Bug 1866788 - Upgrade steps from 4.3 to 4.4 are missing for HE deployment
Summary: Upgrade steps from 4.3 to 4.4 are missing for HE deployment
Keywords:
Status: CLOSED DUPLICATE of bug 1802650
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.4.1
Hardware: All
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Steve Goodman
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-08-06 11:10 UTC by Ulhas Surse
Modified: 2020-08-18 05:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-08-16 07:13:45 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ulhas Surse 2020-08-06 11:10:20 UTC
Description of problem:
In the upgrade documentation of 4.3 to 4.4 Hosted Engine deployment, it seems some more clear steps are required. 

Version-Release number of selected component (if applicable):
RHV 4.4

How reproducible:
Always

Actual results:
6.4. Upgrading the Red Hat Virtualization Manager from 4.3 to 4.4
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/upgrading_the_manager_to_4-4_4-3_she

Expected results:
The points required are:

 1] Point 2 should talk about whether the global maintenance mode should be enabled since there will be more than one host in the HE cluster. Because in the next step, we are asking to stop ovirt-engine.

 2] Is only ovirt-engine stop is enough. I believe the HE VM should also be shutdown. This should be before local maintenance

 3] In point 6 it is asked to enable local (considering the HE VM was not down) will it not restart on the other host? 

Please include/ modify the documentation accordingly. 

Additional info:

Comment 2 Marina Kalinin 2020-08-06 19:45:22 UTC
Honestly, I do not understand why local maintenance and not global maintenance. IMO, it should be just global maintenance first of all.


Note You need to log in before you can comment on or make changes to this bug.