Bug 1474870

Summary: [Docs][Upgrade] Update Upgrade Guide to recommend VMs power cycle
Product: Red Hat Enterprise Virtualization Manager Reporter: Jiri Belka <jbelka>
Component: DocumentationAssignee: Byron Gravenorst <bgraveno>
Status: CLOSED CURRENTRELEASE QA Contact: Emma Heftman <eheftman>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 4.0.7CC: bgraveno, fgarciad, inetkach, klaas, lbopf, lsurette, michal.skrivanek, rbalakri, srevivo, ykaul, ylavi
Target Milestone: ovirt-4.1.5Keywords: EasyFix, Reopened
Target Release: ---Flags: lsvaty: testing_plan_complete-
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-11-13 03:25:05 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 Jiri Belka 2017-07-25 14:24:09 UTC
Description of problem:

we recommend to power cycle all VMs after changing cluster level soon.

but we do not have such info in Upgrade Guides[1][2].

Michal Skrivanek noted the power cycle in a thread with following
text:

~~~
note that for migration improvements to be effective (4.0 feature) the
cluster level would need to be further updated to 4.0 compatibility
and migration policy would need to be changed from “Legacy” then. This
4.0 cluster update need to happen only AFTER all the former originally
3.5 VMs are power cycled and running properly as 3.6 VMs! Otherwise
the same migration configuration tweaks may need to be applied (I
suppose it’s mainly the bandwidth speed, but pending confirmation)
~~~

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

Comment 1 Jiri Belka 2017-07-25 14:26:35 UTC
Michal, could you prepare a text for this recommendation explaining
reasoning for this please?

Comment 2 Michal Skrivanek 2017-07-25 14:29:48 UTC
the text is in bug 1356027 doc text

Comment 3 Lucy Bopf 2017-07-28 08:33:57 UTC
Assigning to Byron for review.

Comment 7 Byron Gravenorst 2017-08-14 03:24:29 UTC
Implemented review comments and merged.

Comment 9 Igor Netkachev 2017-11-07 15:32:12 UTC
Hello,

Reopening this one per customer's request because in sentence "This is achieved by restarting the virtual machine" the word 'restart' is oftem read by customers as 'reboot', and those are 2 different things: 'reboot' could be thought of as an event triggered from inside guest OS (hence the same qemu process is still running on hypervisor even though guest OS inside has been reinitialized), and 'restart' is an action initiated from GUI or REST API (and implies shutting down current qemu process and starting new one instead, so that new qemu process could pick up new functionality of the new DC/cluster level).

I would suggest to clarify term 'restart' in the above doc, e.g.:

"This is achieved by restarting the virtual machine (power-cycle, or cold restart, initiated via Manager UI or REST API call, in contrast to 'warm reboot' initiated from within guest operating system)"

Please let me know what you think.

Please let me know if you have any further questions or concerns.

--
Kind Regards,
Igor Netkachev
Technical Support Engineer
Red Hat Global Support Services