Bug 1691509 - [RFE] Provide a way for heketi to start in an "administrative mode"
Summary: [RFE] Provide a way for heketi to start in an "administrative mode"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: heketi
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: OCS 3.11.z Batch Update 3
Assignee: John Mulligan
QA Contact: Nitin Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-03-21 18:56 UTC by John Mulligan
Modified: 2019-06-13 13:47 UTC (History)
10 users (show)

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.
Clone Of:
Environment:
Last Closed: 2019-06-13 13:47:35 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1408 0 None None None 2019-06-13 13:47:40 UTC

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
Note You need to log in before you can comment on or make changes to this bug.