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:
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"}
Fixed in RHGS 3.3 documentation.