Bug 822983 - 13.3.3. Manually Fencing or Isolating a Host should provide a clear warning about misuse
Summary: 13.3.3. Manually Fencing or Isolating a Host should provide a clear warning a...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation
Version: 3.1.0
Hardware: All
OS: All
unspecified
high
Target Milestone: ---
: ---
Assignee: Cheryn Tan
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 815452
TreeView+ depends on / blocked
 
Reported: 2012-05-18 16:59 UTC by Dan Yasny
Modified: 2015-09-22 13:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 17:25:45 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
GUI warning example (33.29 KB, image/png)
2012-05-18 16:59 UTC, Dan Yasny
no flags Details

Description Dan Yasny 2012-05-18 16:59:56 UTC
Created attachment 585453 [details]
GUI warning example

Description of problem:
"Confirm Hist has been Rebooted" is a dangerous option, and the GUI shows a big red warning about the dangers of sing this option without actually fencing the host.

The Admin guide should provide the same warning as in the GUI and re-stress the danger of marking a host as fenced, when it might be still running. Lack of warning can lead to a VM image corruption.



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

Comment 1 Cheryn Tan 2012-09-20 07:30:31 UTC
Added:

"Warning
Do not use the Confirm host has been rebooted option unless you have manually rebooted the host. Using this option while the host is still running can lead to a virtual machine image corruption."


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