Bug 1905296

Summary: [upgrade] Remove blacklist section and add a note on fixing LVM filter
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: SATHEESARAN <sasundar>
Component: DocumentationAssignee: Disha Walvekar <dwalveka>
Status: CLOSED CURRENTRELEASE QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: rhhiv-1.8CC: asriram, dwalveka, rhs-bugs, storage-doc, storage-qa-internal
Target Milestone: ---Keywords: ZStream
Target Release: RHHI-V 1.8.z Async Update   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-02-08 16:53:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1898439    

Description SATHEESARAN 2020-12-08 01:14:21 UTC
Describe the issue:
--------------------
There are few changes required in the upgrade guide, as RHVH modified few LVM filter related items, which breaks the backup configuration restore process.

Describe the task you were trying to accomplish:
-------------------------------------------------
fix documentation for errors during ugrade

Suggestions for improvement:
-----------------------------
1. Remove blacklist section under the following section:
          - Section 4.4.7, 
          - Section 4.4.11, point 4
This is because blacklisting the devices is automatically implemented, when
generating new LVM filters

2. Add a note to remove existing LVM filter before backup restore, and regenerate
filter post restoration in the following sections
     - Section 4.4.9 , 
           Add the first point
               1. Remove the existing LVM filter, to allow using the existing        
                  Physical Volumes (PVs)
                    # sed -i /^filter/d /etc/lvm/lvm.conf
           Add the last point to regenerate LVM filter
               6. Regenerate new LVM filters for newly identified PVs
                    # vdsm-tool config-lvm-filter -y
         
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#restore-files

Chapter/Section Number and Title:
---------------------------------
Upgrade guide

Product Version:
-----------------
1.8

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

Comment 1 SATHEESARAN 2020-12-08 01:24:01 UTC
Apart from above said 2 changes, there are couple of more changes required to fix upgrade issues.

change#1
----------
Section 4.4.10,  point 1 shows the playbook he.yml to be created. It has a small change in the last line

<snip>
---
- name: Deploy oVirt hosted engine
  hosts: localhost
  roles:
    - role: ovirt.ovirt.hosted_engine_setup      <---- Note it should ovirt.ovirt. earlier it was ovirt.
</snip>

change#2
----------
Section 4.4.10 - point 2 show the list of options which needs one more option:
"he_vcpus": "4"

The example should be:
# cat /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/he_gluster_vars.json

{
  "he_appliance_password": "password",
  "he_admin_password": "password",
  "he_domain_type": "glusterfs",
  "he_fqdn": "hostedengine.example.com",
  "he_vm_mac_addr": "00:18:15:20:59:01",
  "he_default_gateway": "19.70.12.254",
  "he_mgmt_network": "ovirtmgmt",
  "he_storage_domain_name": "HostedEngine",
  "he_storage_domain_path": "/newengine",
  "he_storage_domain_addr": "host1.example.com",
  "he_mount_options": "backup-volfile-servers=host2.example.com:host3.example.com",
  "he_bridge_if": "eth0",
  "he_enable_hc_gluster_service": true,
  "he_mem_size_MB": "16384",
  "he_cluster": "Default",
  "he_restore_from_file": "/root/engine-backup.tar.gz",   <---- Note there is a comma added to the end
  "he_vcpus": "4"     <--------- note new option added
  }

Comment 2 SATHEESARAN 2020-12-08 01:34:54 UTC
There is one last change regarding the cluster compatibility updation.

Section 4.4.14 says - "Select Compute → Clusters → Select the cluster Default → Edit → update Compatibility Version to 4.4 → OK."

Please update that to 4.5

Comment 5 SATHEESARAN 2020-12-08 13:03:52 UTC
Thanks Disha.

Verified the doc link and the content now has relevant information