Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1353537

Summary:	hosted-engine --vm-status --json does not show global maintenance mode
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ryan Barry <rbarry>
Component:	ovirt-hosted-engine-setup	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED ERRATA	QA Contact:	Artyom <alukiano>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.0.0	CC:	gklein, lsurette, melewis, sbonazzo, stirabos, ykaul, ylavi
Target Milestone:	ovirt-4.0.1	Keywords:	Triaged
Target Release:	4.0.1
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	With this update, hosted-engine --vm-status --json now shows global maintenance mode.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 21:02:44 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Integration	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ryan Barry 2016-07-07 12:07:31 UTC

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-2.0.0-1.el7.centos.noarch

How reproducible:
100%

Steps to Reproduce:
1. Put the cluster in global maintenance mode
2. Run "hosted-engine --vm-status --json"

Actual results:
No global maintenance field

Expected results:
Global maintenance should be shown

Comment 4 Artyom 2016-07-21 10:39:22 UTC

Verified on ovirt-hosted-engine-setup-2.0.1-1.el7ev.noarch

Global maintenance disabled:
# hosted-engine --vm-status --json
{"1": {"live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=6336 (Thu Jul 21 13:37:32 2016)\nhost-id=1\nscore=3400\nmaintenance=False\nstate=EngineUp\nstopped=False\n", "hostname": "rose05.qa.lab.tlv.redhat.com", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "d0d04c62", "host-ts": 6336}, "global_maintenance": false}

# hosted-engine --set-maintenance --mode=global
# hosted-engine --vm-status --json
{"1": {"live-data": true, "extra": "metadata_parse_version=1\nmetadata_feature_version=1\ntimestamp=6399 (Thu Jul 21 13:38:35 2016)\nhost-id=1\nscore=3400\nmaintenance=False\nstate=EngineUp\nstopped=False\n", "hostname": "rose05.qa.lab.tlv.redhat.com", "host-id": 1, "engine-status": {"health": "good", "vm": "up", "detail": "up"}, "score": 3400, "stopped": false, "maintenance": false, "crc32": "6da399ca", "host-ts": 6399}, "global_maintenance": true}

Comment 6 errata-xmlrpc 2016-08-23 21:02:44 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHEA-2016-1744.html