Bug 1467585 - [Docs][Upgrade][4.1] Missing info about engine-upgrade-check
Summary: [Docs][Upgrade][4.1] Missing info about engine-upgrade-check
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.1.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.6
: ---
Assignee: Byron Gravenorst
QA Contact: Megan Lewis
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 09:38 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-11-08 03:33:49 UTC
oVirt Team: Docs
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jiri Belka 2017-07-04 09:38:06 UTC
Description of problem:
https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html/upgrade_guide/upgrading_to_red_hat_virtualization_manager_4.1 doesn't mention engine-upgrade-check but we mention it for updates of micro releases in same minor release.

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

How reproducible:
100%

Steps to Reproduce:
1. check if '3.2. Upgrading to Red Hat Virtualization Manager 4.1' mentions engine-upgrade-check
2.
3.

Actual results:
missing

Expected results:
should be there

Additional info:

Comment 1 Lucy Bopf 2017-07-12 02:04:23 UTC
Assigning to Byron for review.

Byron, we've never included engine-upgrade-check in the context of a version-to-version upgrade before, so it might be worth confirming what the expected user behaviour is (e.g. 4.1 is released, does a customer on 4.0 need to run engine-upgrade-check to know that 4.1 is available, if they have to enable the 4.1 repos to do so anyway?)


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