Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1685522

Summary: Instead of editing the template, use 'oc process heketi IMAGE_VERSION=v3.11' etc
Product: Red Hat Gluster Storage Reporter: Niels de Vos <ndevos>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: Bhavana <bmohanra>
Status: ASSIGNED --- QA Contact: storage-qa-internal <storage-qa-internal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: asriram, bmohanra, knarra, rhs-bugs, sankarshan, storage-doc
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1694089    

Description Niels de Vos 2019-03-05 12:06:21 UTC
Description of problem:
The OCS Deployment Guide describes to edit the heketi template under

    6.1.2. Upgrading cns-deploy and Heketi Server

The command 'oc edit template heketi' should not be done. Instead, we should use the template as a template, and fill the variables though 'oc process' as that is the OpenShift practise.

Version-Release number of selected component (if applicable): as of today

Additional info:
The 'oc edit template heketi' commands should be removed. The existing 'oc process heketi' command should get extended with the parameters and values that the template should consume:

    oc process heketi IMAGE_VERSION=v3.11 | oc create -f -

Additional parameters can be placed at the end of the 'oc process' command.

Comment 1 RamaKasturi 2019-04-05 12:50:22 UTC
I do not see any customer facing issues with the current approach given in the doc so not acking this for 3.11.3