Bug 1467577 - [Docs][Upgrade] Revise the Red Hat Virtualization 4.1 Upgrade Considerations
Summary: [Docs][Upgrade] Revise the Red Hat Virtualization 4.1 Upgrade Considerations
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.3
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ovirt-4.1.4
: ---
Assignee: Byron Gravenorst
QA Contact: Tahlia Richardson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 09:07 UTC by Jiri Belka
Modified: 2019-05-07 12:55 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-17 05:22:55 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiri Belka 2017-07-04 09:07:06 UTC
Description of problem:

https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/chap-upgrading_to_red_hat_virtualization_4.1#Red_Hat_Virtualization_4.1_Upgrade_Considerations states:

"Upgrading to version 4.1 can only be performed from version 4.0

    To upgrade a version of Red Hat Virtualization earlier than 4.0 to Red Hat Virtualization 4.1, you must sequentially upgrade to later versions of Red Hat Virtualization before upgrading to the latest version. For example, if you are using Red Hat Enterprise Virtualization 3.6, you must upgrade to the latest minor version of Red Hat Virtualization 4.0 before you can upgrade to Red Hat Virtualization 4.1. See the Upgrade Guide for Red Hat Virtualization 4.0 for instructions to upgrade to the latest 4.0 minor version.
    The data center and cluster compatibility version must be at version 4.0 before performing the upgrade."

The whole above section is incorrect, it seems like copy from 4.0.

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

How reproducible:
100%

Steps to Reproduce:
1. read 3.1. Red Hat Virtualization 4.1 Upgrade Considerations contains incorrect info
2.
3.

Actual results:
incorrect info about must to have 4.0 DC/CL compat level before upgrading to 4.1

Expected results:
doc should be correct

Additional info:

Comment 1 Lucy Bopf 2017-07-05 00:50:21 UTC
Hi Jiri,

What do you suggest that we change this to? My understanding is that this note is correct; we only support upgrading to 4.1 from 4.0, not from 3.6 or earlier. Is this no longer the case?

Comment 2 Yaniv Lavi 2017-07-10 14:53:27 UTC
The manager update needs to be stepped (example 3.6->4.0->4.1).
The hosts are not stepped (3.6->4.1). You need to upgrade to latest host from the channel.

In a 4.1 manager, you can still have 3.6 and 4.0 clusters and this is not an issue.

This is urgent, please fix.

Comment 3 Lucy Bopf 2017-07-11 05:11:27 UTC
Assigning to Byron for review.

Byron, see Yaniv's comment 2. We just need to update the wording slightly to capture that.

Comment 7 Byron Gravenorst 2017-07-16 23:53:31 UTC
Moving to ON_QA.


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