Bug 1449698

Summary: [HCI] - hosted-engine --vm-status output has to be changed
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: DocumentationAssignee: Laura Bailey <lbailey>
Status: CLOSED CURRENTRELEASE QA Contact: RamaKasturi <knarra>
Severity: medium Docs Contact:
Priority: unspecified    
Version: rhgs-3.2CC: dchaplyg, msivak, rhs-bugs, sabose, sankarshan, sasundar, storage-doc, storage-qa-internal
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-08-29 04:10:52 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: 1277939    

Description RamaKasturi 2017-05-10 13:20:28 UTC 
Document URL: https://doc-stage.usersys.redhat.com/documentation/en-us/red_hat_gluster_storage/3.2/html-single/maintaining_red_hats_hyper-converged_infrastructure/#configure-encryption

Section Number and Name: 4.1. CONFIGURING TLS/SSL USING SELF-SIGNED CERTIFICATES

Describe the issue: In point no.13 of the above section  i see that hosted-engine --vm-status is put as same in all the nodes.

Suggestions for improvement: hosted-engine --vm-status has to be changed as vm can be up and running only on one host and the other host will not report the engine status as good on all nodes.

hosted-engine --vm-status | grep 'Engine status'
Engine status                      : {"health": "good", "vm": "up", "detail": "up"}
Engine status                      : {"health": "good", "vm": "up", "detail": "up"}
Engine status                      : {"health": "good", "vm": "up", "detail": "up"}

hosted-engine --vm-status | grep 'Engine status'
Engine status                      : {"health": "good", "vm": "up", "detail": "up"}
Engine status                      : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}
Engine status                      : {"reason": "vm not running on this host", "health": "bad", "vm": "down", "detail": "unknown"}

Additional information:
Comment 9 RamaKasturi 2017-05-16 07:42:09 UTC 
Verified in the link provided in comment 8 and the changes looks good to me.

Below is the content in the doc.

hosted-engine --vm-status | grep 'Engine status'
Engine status   : {"health": "good", "vm": "up", "detail": "up"}
Engine status   : {"reason": "vm not running on this host",
  "health": "bad", "vm": "down", "detail": "unknown"}
Engine status   : {"reason": "vm not running on this host",
  "health": "bad", "vm": "down", "detail": "unknown"}
Comment 10 Laura Bailey 2017-08-29 04:10:52 UTC 
Fixed in RHGS 3.3 documentation.