Bug 1900155 - [RHHI-V] Add few more steps to the minor version update section
Summary: [RHHI-V] Add few more steps to the minor version update section
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: Documentation
Version: rhhiv-1.8
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHHI-V 1.8.z Async Update
Assignee: Laura Bailey
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks: 1898439
TreeView+ depends on / blocked
 
Reported: 2020-11-21 02:13 UTC by SATHEESARAN
Modified: 2021-01-13 12:12 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-13 12:12:41 UTC
Embargoed:


Attachments (Terms of Use)

Description SATHEESARAN 2020-11-21 02:13:37 UTC
Describe the issue:
-------------------
The minor version update for RHHI-V 1.8 is documented and this procedure holds true only for the customers that update from RHV 4.4.1.

For those customers that update from RHV 4.4.2, customers need not perform some hard process and can update it in a simple way, so introduce one more section calling it as - 'Update from RHV 4.4.2', and existing content should go under 'updating from RHV 4.4.1'

Describe the task you were trying to accomplish:
------------------------------------------------
Adding more clarity to minor version update section, with the release of RHV 4.4.3

Suggestions for improvement:
-------------------------------
This will be added as a separate comment

Document URL:
-------------
https://access.redhat.com/documentation/en-us/red_hat_hyperconverged_infrastructure_for_virtualization/1.8/html-single/upgrading_red_hat_hyperconverged_infrastructure_for_virtualization/index#upgrade-hyperconverged-hosts

Chapter/Section Number and Title:
----------------------------------
5.4. Upgrading the hyperconverged hosts

Product Version:
----------------
RHHI-V 1.8

Environment Details:
---------------------
RHV 4.4.2 and RHHI-V 1.8

Any other versions of this document that also needs this update:
----------------------------------------------------------------
No

Comment 1 SATHEESARAN 2020-11-21 02:44:46 UTC
Changes required
-----------------

CHANGE #1
===========
1. Proposing section 5.4 should to contain 2 sub-section, with a generic statement.

Red Hat Virtualization Node version can be obtained in the following way.
# cat /etc/os-release | grep PRETTY_NAME
Example:
# cat /etc/os-release | grep PRETTY_NAME
PRETTY_NAME="Red Hat Virtualization Host 4.4.2 (el8.2)"

Based on the existing  version of Red Hat Virtualization Node, choose the update section

5.4.1 - Updating Red Hat Virtualization Node 4.4.1
<here goes the existing content>

5.4.2 - Updating Red Hat Virtualization Node 4.4.2 and above

1. Upgrade the hyperconverged host.

    i. In the Manager, click Compute → Hosts and select a node.
    ii. Click Installation → Upgrade.
    iii.Click OK to confirm the upgrade.

    Wait for the upgrade to complete, and for the host to become available again. 

2. Verify self-healing is complete before upgrading the next host.

    i. Click the name of the host.
    ii. Click the Bricks tab.
    iii. Verify that the Self-Heal Info column of all bricks is listed as OK before upgrading the next host. 

3. Update other hosts in the cluster, by selecting one at a time for upgrade, and perform above steps 1,2



CHANGE #2
==========
Include one more section - POST UPGRADE - specifically for customers updating from Red Hat Virtualization Host 4.4.2
Fact is that customers updating RHVH 4.4.2 will have to update the cluster and Data center compatibility to 4.5

5.5 Post update tasks
----------------------
If Red Hat Virtualization is updated from RHV 4.4.2, make sure the cluster and datacenter compatibility version
are set to 4.5

1. Update cluster compatibility

    When all hosts are upgraded, update cluster and datacenter compatibility setting.

    i. In the Red Hat Virtualization Administration Portal, click Cluster and select the cluster (Default).
    Click Edit.
    ii. Update the value of Cluster compatibility version to 4.5 and save. 
    Note: Updating the cluster compatibility will be complete with the rebooting of Virtual Machines.
          Virtual Machines can be rebooted during the planned maintenance window later
    iii. Go to Compute -> Data Centers -> Edit, update the value of 'compatibility version' to 4.5

Comment 11 SATHEESARAN 2020-12-08 13:14:14 UTC
Verified with the internal doc link.

The doc contains the right set of information as suggested in comment0


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