Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1193556 - [Docs][Tech] Document rhevm-shell command for "confirm host has been rebooted"
[Docs][Tech] Document rhevm-shell command for "confirm host has been rebooted"
Status: CLOSED CURRENTRELEASE
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: Documentation (Show other bugs)
3.6.0
x86_64 Linux
unspecified Severity medium
: ---
: 3.6.0
Assigned To: Julie
Tahlia Richardson
infra
: FutureFeature
Depends On:
Blocks: 1207472
  Show dependency treegraph
 
Reported: 2015-02-17 10:25 EST by Martin Pavlik
Modified: 2016-02-10 14:14 EST (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-04-29 01:27:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Infra
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Martin Pavlik 2015-02-17 10:25:38 EST
Description of problem:
add command for "confirm host has been rebooted" to rhevm-shell

at the moment there is no possibility to "confirm host has been rebooted" via cli

if SPM host becomes non-responsive, it is impossible to make RHEV-M choose new SPM because of this
Comment 1 Juan Hernández 2015-02-17 10:39:35 EST
Doesn't the following command work?

  # action host myhost fence --fence_type manual

In theory that performs the same action that the "confirm host has been rebooted" action of the GUI. Please verify and close as NOTABUG if it works correctly.
Comment 2 Martin Pavlik 2015-02-17 10:53:02 EST
it works, 

@Juan 
how is the user supposed to know that this action equals "confirm host has been rebooted"


[RHEVM shell (connected)]# action host XXXXXX.redhat.com fence --fence_type manual

fence_type  : manual
host-id     : 00d9f14d-87b6-4613-b92e-fdd49e2a2615
status-state: complete
Comment 3 Juan Hernández 2015-02-17 10:57:08 EST
The only way to make that clear for users is documentation. I'm moving the bug to the documentation component.

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