Bug 1691509

Summary:	[RFE] Provide a way for heketi to start in an "administrative mode"
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	John Mulligan <jmulligan>
Component:	heketi	Assignee:	John Mulligan <jmulligan>
Status:	CLOSED ERRATA	QA Contact:	Nitin Goyal <nigoyal>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	akrishna, hchiramm, knarra, kramdoss, madam, nigoyal, rhs-bugs, rtalur, sankarshan, storage-qa-internal
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	heketi-8.0.0-11.el7rhgs	Doc Type:	Enhancement
Doc Text:	Previous versions of Heketi allowed setting an "administrative mode" using the heketi-cli tool. These modes could be used to prepare the server for shut down or restrict access to locally issued commands. However, these modes could only be applied after the server was started. In some circumstances, allowing the server to start normally before the administrative mode was set opened a window for undesired changes to be requested by clients. Now, an initial state at startup via the HEKETI_DEFAULT_STATE environment variable can be provided to Heketi.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-13 13:47:35 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:

Description John Mulligan 2019-03-21 18:56:56 UTC

Description of problem:

Sometimes when debugging an issue or preparing for a major change to the system it is useful to have heketi running but not answering requests from other clients. For example, an administrator needs to stop heketi in preparation for an upgrade but wants to be able to run heketi commands when the server starts back up without the system immediately reacting to PVCs created in OpensShift.


Expected results:

Create a mechanism through which the user or support staff can allow heketi to start but not respond to all commands after starting up.

Comment 3 RamaKasturi 2019-03-28 12:52:26 UTC

Acking this bug for 3.11.3

Comment 10 Anjana KD 2019-06-03 12:58:46 UTC

Kindly review the updated doc text.

Comment 12 Anjana KD 2019-06-04 12:05:32 UTC

Thanks, John.

Comment 14 errata-xmlrpc 2019-06-13 13:47:35 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://access.redhat.com/errata/RHBA-2019:1408