Bug 1404374 - [RHV] Getting started link may create small confusion for customers
Summary: [RHV] Getting started link may create small confusion for customers
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 4.0.0
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: rhev-docs@redhat.com
QA Contact: rhev-docs@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-12-13 16:58 UTC by Shivraj
Modified: 2022-06-30 08:35 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-07 07:38:50 UTC
oVirt Team: Docs
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-46800 0 None None None 2022-06-30 08:35:06 UTC

Description Shivraj 2016-12-13 16:58:54 UTC 
Description of problem:

Link https://access.redhat.com/products/red-hat-virtualization#getstarted
gives steps for setting up RHV environment but at step 6 it is not exclusively mentioned that hypervisor installation has to be done on separate physical server.
Due to confusion User may install hypervisor ISO on the same machine where he already installed RHV manager machine.

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

How reproducible:
N.A.

Steps to Reproduce:
N.A.

Actual results:
No exclusive mention to install hypervisor on separate physical host

Expected results:
Exclusively mention to install hypervisor on separate physical host

Additional info:
https://access.redhat.com/discussions/2805801
Comment 1 Yaniv Lavi 2017-02-07 07:38:50 UTC 
We don't have resources to handle this and the customer can understand that reinstalling the host will cause him to lose the previous installation.
Note You need to log in before you can comment on or make changes to this bug.