Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1888620

Summary:	Fixes around advanced virtualization module version and installation/upgrade
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Martin Perina <mperina>
Component:	Documentation	Assignee:	Steve Goodman <sgoodman>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.4.0	CC:	chhu, delfassy, emarcus, gveitmic, lleistne, lsurette, mhicks, sgoodman, srevivo
Target Milestone:	ovirt-4.4.3	Keywords:	Documentation, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-12 15:26:12 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Perina 2020-10-15 11:27:31 UTC

As RHV 4.4.3 will require RHEL 8.3 we need to perform following changes around advanced virtualization module versions in RHV documentation:

I. Change advanced virtualization module version to 8.3 in below chapters:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_command_line/installing_the_self-hosted_engine_deployment_host_she_cli_deploy#Enabling_the_Red_Hat_Enterprise_Linux_Host_Repositories_SHE_deployment_host

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/installing_red_hat_virtualization_as_a_self-hosted_engine_using_the_cockpit_web_interface/installing_the_self-hosted_engine_deployment_host_she_cockpit_deploy#Enabling_the_Red_Hat_Enterprise_Linux_Host_Repositories_SHE_deployment_host



II. Update Manually updating hosts to appendix to use latest advanced virtualization module

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/manually_updating_hosts_minor_updates

We need to add following steps to the procedure for RHEL hypervisors only (below steps are not applicable to RHV-H)

  3. Click Management → Maintenance. (no change)

  4. Get current RHEL version

       cat /etc/redhat-release

  5. Check what version redhat-release package is available

       dnf --refresh info --available redhat-release

     If this is RHEL y-stream upgrade then there will be returned a new package, 
     for example in case of upgrade from 8.2.z to 8.3:

       Available Packages
       Name         : redhat-release
       Version      : 8.3
       Release      : 1.0.el8
       Architecture : x86_64
       Size         : 41 k
       Source       : redhat-release-8.3-1.0.el8.src.rpm
       Repository   : rhel-8.3-nightly-baseos
       Summary      : Red Hat Enterprise Linux release file
       License      : GPLv2
       Description  : Red Hat Enterprise Linux release files

     And user will need to compare version of the package with currently 
     installed version

   6. If this is RHEL 8.3 y-stream upgrade enabled new RHEL AV module

        dnf module reset virt -y
        dnf module enable virt:8.3 -y

      Please replace '8.3' with the version you are upgrading to.

      If there is not a new module available (usually relevant RHEL AV module is 
      released later than RHEL y-stream) or there is an error enabling it, users 
      need to cancel the upgrade!!!

    7. Upgrade packages
     
         dnf upgrade


III. Make manual update of hosts deprecated

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/manually_updating_hosts_minor_updates

  Please below note to the beginning of chapter:

  Manual update of hosts is deprecated, please use either Updating individual hosts method [ https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/updating_individual_hosts_minor_updates ] or Updating all hosts in a cluster method [ https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/upgrade_guide/updating_all_hosts_in_a_cluster_minor_updates ].
  Manual update of hosts doesn't involve important steps performed in above flows such as certificates renewal.

Comment 1 Steve Goodman 2020-10-15 11:45:39 UTC

(In reply to Martin Perina from comment #0)
 
> II. Update Manually updating hosts to appendix to use latest advanced
> virtualization module
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/
> html/upgrade_guide/manually_updating_hosts_minor_updates
> 
> We need to add following steps to the procedure for RHEL hypervisors only
> (below steps are not applicable to RHV-H)
> 
>   3. Click Management → Maintenance. (no change)
> 
>   4. Get current RHEL version
> 
>        cat /etc/redhat-release
> 
>   5. Check what version redhat-release package is available
> 
>        dnf --refresh info --available redhat-release
> 
>      If this is RHEL y-stream upgrade then there will be returned a new
> package, 
>      for example in case of upgrade from 8.2.z to 8.3:
> 
>        Available Packages
>        Name         : redhat-release
>        Version      : 8.3
>        Release      : 1.0.el8
>        Architecture : x86_64
>        Size         : 41 k
>        Source       : redhat-release-8.3-1.0.el8.src.rpm
>        Repository   : rhel-8.3-nightly-baseos
>        Summary      : Red Hat Enterprise Linux release file
>        License      : GPLv2
>        Description  : Red Hat Enterprise Linux release files
> 
>      And user will need to compare version of the package with currently 
>      installed version
> 
>    6. If this is RHEL 8.3 y-stream upgrade enabled new RHEL AV module
> 
>         dnf module reset virt -y
>         dnf module enable virt:8.3 -y
> 
>       Please replace '8.3' with the version you are upgrading to.
> 
>       If there is not a new module available (usually relevant RHEL AV
> module is 
>       released later than RHEL y-stream) or there is an error enabling it,
> users 
>       need to cancel the upgrade!!!
> 
>     7. Upgrade packages
>      
>          dnf upgrade
> 
> 
> III. Make manual update of hosts deprecated
> 
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/
> html/upgrade_guide/manually_updating_hosts_minor_updates
> 
>   Please below note to the beginning of chapter:
> 
>   Manual update of hosts is deprecated, please use either Updating
> individual hosts method [
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/
> html/upgrade_guide/updating_individual_hosts_minor_updates ] or Updating all
> hosts in a cluster method [
> https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/
> html/upgrade_guide/updating_all_hosts_in_a_cluster_minor_updates ].
>   Manual update of hosts doesn't involve important steps performed in above
> flows such as certificates renewal.

On the one hand, we're updating the content (II) but also deprecating it (III).

1. Why not just remove the content altogether?
2. If you want to keep the content but deprecate it, when do you want to remove it?

Comment 2 Martin Perina 2020-10-15 12:22:22 UTC

> 
> On the one hand, we're updating the content (II) but also deprecating it
> (III).
> 
> 1. Why not just remove the content altogether?

Many customers are used to manual upgrades, so even though we want manual upgrade to be deprecated, we need to make sure that steps are as correct as possible otherwise we may have customer cases around upgrades increased.

> 2. If you want to keep the content but deprecate it, when do you want to
> remove it?

I suggest to leave it deprecated till the end of RHV

Comment 3 Steve Goodman 2020-10-26 12:02:40 UTC

(In reply to Martin Perina from comment #2)
> > 
> > On the one hand, we're updating the content (II) but also deprecating it
> > (III).
> > 
> > 1. Why not just remove the content altogether?
> 
> Many customers are used to manual upgrades, so even though we want manual
> upgrade to be deprecated, we need to make sure that steps are as correct as
> possible otherwise we may have customer cases around upgrades increased.
> 
> > 2. If you want to keep the content but deprecate it, when do you want to
> > remove it?
> 
> I suggest to leave it deprecated till the end of RHV

I have never seen a piece of documentation deprecated, only part of the application e.g. options, storage domain types, etc. I propose that we add a Caution stating that this procedure is unsupported instead.

Comment 4 Steve Goodman 2020-10-26 15:21:32 UTC

>      for example in case of upgrade from 8.2.z to 8.3:
> 
>        Available Packages
>        Name         : redhat-release
>        Version      : 8.3
>        Release      : 1.0.el8
>        Architecture : x86_64
>        Size         : 41 k
>        Source       : redhat-release-8.3-1.0.el8.src.rpm
>        Repository   : rhel-8.3-nightly-baseos
>        Summary      : Red Hat Enterprise Linux release file
>        License      : GPLv2
>        Description  : Red Hat Enterprise Linux release files
> 
>      And user will need to compare version of the package with currently 
>      installed version
> 
>    6. If this is RHEL 8.3 y-stream upgrade enabled new RHEL AV module
...
>       If there is not a new module available (usually relevant RHEL AV
> module is 
>       released later than RHEL y-stream) or there is an error enabling it,
> users 
>       need to cancel the upgrade!!!

What will the output look like when there IS a new AV stream available?

Comment 10 Steve Goodman 2020-10-29 08:10:42 UTC

Lucie,

Can you please verify this one?

Comment 11 Petr Matyáš 2020-10-30 08:33:25 UTC

Looks good.

Comment 12 Steve Goodman 2020-11-02 16:46:19 UTC

Eli,

Can you please do peer review?

https://gitlab.cee.redhat.com/rhci-documentation/docs-Red_Hat_Enterprise_Virtualization/-/merge_requests/1841

Comment 13 Eli Marcus 2020-11-05 14:22:38 UTC

(In reply to Steve Goodman from comment #12)
> Eli,
> 
> Can you please do peer review?
> 
> https://gitlab.cee.redhat.com/rhci-documentation/docs-
> Red_Hat_Enterprise_Virtualization/-/merge_requests/1841

Done looks fine

Comment 14 Steve Goodman 2020-11-10 05:36:14 UTC

Merged. Will publish for 4.4.3.

Comment 15 Steve Goodman 2020-11-12 15:22:03 UTC

*** Bug 1886721 has been marked as a duplicate of this bug. ***

Comment 16 Steve Goodman 2020-11-12 15:25:55 UTC

Published. The information is relevant already.