Bug 822983

Summary: 13.3.3. Manually Fencing or Isolating a Host should provide a clear warning about misuse
Product: Red Hat Enterprise Virtualization Manager Reporter: Dan Yasny <dyasny>
Component: DocumentationAssignee: Cheryn Tan <chetan>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: acathrow, dyasny, gklein, jskeoch, rlandman, sgordon, yeylon
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-04 17:25:45 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 815452    
Attachments:
Description Flags
GUI warning example none

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."