Bug 1359572

Summary: [Docs][SHE] The restore SHE chapter needs to be reviewed for 4.0
Product: Red Hat Enterprise Virtualization Manager Reporter: Julie <juwu>
Component: DocumentationAssignee: rhev-docs <rhev-docs>
Status: CLOSED DUPLICATE QA Contact: rhev-docs <rhev-docs>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.0.0CC: bgraveno, lbopf, lsurette, nsednev, rbalakri, srevivo, stirabos, ykaul, ylavi
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-06-13 07:38:53 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Docs RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Julie 2016-07-25 03:53:24 UTC
Documentation Link:
https://access.redhat.com/documentation/en/red-hat-virtualization/4.0-beta/self-hosted-engine-guide/62-restoring-the-self-hosted-engine-environment

The current restore procedure has not been tested using the the virtual appliance. The instructions need to be reviewed for the 4.0 release.

Kind regards,
Julie

Comment 1 Yaniv Lavi 2016-12-05 08:32:55 UTC
Need to add someone from engineering to review and update link to working one.

Comment 3 Byron Gravenorst 2016-12-06 00:26:28 UTC
Hi Nikolai,

Yaniv mentioned in a meeting that I should ask you to please review this content. I've updated the link to the documentation (comment 2).

We need to review the entire section (6.2).

Kind regards,

Comment 4 Nikolai Sednev 2017-01-05 01:15:26 UTC
Please tak a look at the https://bugzilla.redhat.com/show_bug.cgi?id=1397810#c2.
I've followed steps 1-12 and succeeded.

Comment 5 Yaniv Lavi 2017-01-24 12:59:31 UTC
Can you please review the link in comment 2 and provide feedback on that? 
We can not make sense from the bug you mentioned.

Comment 6 Nikolai Sednev 2017-01-24 13:45:52 UTC
1-Deployed HE on pair of 3.6's RHEVH7.2, over NFS and added two data storage domains.
2-Got hosted-storage auto-imported.
3-Installed on the engine the latest rhev-hypervisor7.noarch 0:7.3-20161028.1.el6ev
4-Updated both hosts from RHEV Hypervisor - 7.2 - 20160920.1.el7ev 
5-Followed the https://access.redhat.com/documentation/en/red-hat-virtualization/4.0/single/self-hosted-engine-guide/#Upgrading_the_Self-Hosted_Engine to upgrade my HE mixed (RHEVH&RHEL) environment environment.
Engine was running on 4.0.6 RHEL7.3 host, while it was SPM.
Engine had disk at the size of 200Gig, while was still in 3.6.10
6-Upgraded my environment from 3.6.10 to 4.0.6.2-0.1.el7ev and then successfully rolled back to 3.6.10.
7-Got the engine with these components:
rhevm-dependencies-4.0.0-1.el7ev.noarch
rhevm-spice-client-x86-msi-4.0-3.el7ev.noarch
rhevm-4.0.6.2-0.1.el7ev.noarch
rhevm-spice-client-x64-msi-4.0-3.el7ev.noarch
rhevm-doc-4.0.6-1.el7ev.noarch
rhev-guest-tools-iso-4.0-6.el7ev.noarch
rhevm-branding-rhev-4.0.0-6.el7ev.noarch
rhevm-setup-plugins-4.0.0.3-1.el7ev.noarch
rhevm-guest-agent-common-1.0.12-3.el7ev.noarch
Linux version 3.10.0-514.el7.x86_64 (mockbuild.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Wed Oct 19 11:24:13 EDT 2016
Linux 3.10.0-514.el7.x86_64 #1 SMP Wed Oct 19 11:24:13 EDT 2016 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.3 (Maipo)
8-Set hosts to global maintenance.
9-Stopped engine's VM and verified that it is not running on any HE-host.
10-Successfully executed rollback-upgrade back to 3.5.6 old engine.
11-Returned hosts from global maintenance to none.
12-Logged in successfully to WEBADMIN of  Red Hat Enterprise Virtualization Manager Version: 3.5.8-0.1.el6ev.

Comment 7 Yaniv Lavi 2017-01-31 08:04:34 UTC
Can you please help with the review?

Comment 8 Simone Tiraboschi 2017-01-31 09:51:20 UTC
(In reply to Yaniv Dary from comment #7)
> Can you please help with the review?

OK

Comment 10 Yaniv Lavi 2017-06-13 07:38:53 UTC

*** This bug has been marked as a duplicate of bug 1420604 ***