Bug 1709684

Summary: Upgrade playbook is not upgrading heketi-client installed on master node
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Nitin Goyal <nigoyal>
Component: doc-Container_Native_Storage_with_OpenShiftAssignee: storage-doc
Status: CLOSED WONTFIX QA Contact: storage-qa-internal <storage-qa-internal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: asambast, asriram, hchiramm, jarrpa, jmulligan, knarra, kramdoss, madam, rhs-bugs, sarumuga, storage-doc, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-27 15:24:32 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:
Bug Depends On:    
Bug Blocks: 1703695    

Description Nitin Goyal 2019-05-14 07:16:01 UTC 
Description of problem:
Upgrade playbook is not upgrading heketi-client installed on master node

Version-Release number of selected component (if applicable):
openshift-ansible-3.11.115-1.git.0.6e67897.el7.noarch

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
It is not upgrading heketi-client

Expected results:
It should upgrade heketi-client

Additional info:
# rpm -q heketi-client
heketi-client-7.0.0-11.el7rhgs.x86_64
Comment 2 Jose A. Rivera 2019-05-14 13:17:45 UTC 
I think a more appropriate solution would be to just be rid of any instructions to install heketi-client and make users always use the heketi CLI in the container. Since we are now only supporting containerized heketi, this will work across all installations.
Comment 4 Jose A. Rivera 2019-07-02 17:41:24 UTC 
Customers who are currently using an external heketi-client will continue to work as-is, they just won't have access to new features in the heketi server. If they want the new features, they can switch to using the built-in client in the container. If they have automation that makes use of heketi-client, the change is fairly trivial in that all you'd do is prepend an "oc exec" command to the heketi-client line and call it a day.
Comment 5 Jose A. Rivera 2019-07-02 17:41:59 UTC 
Setting devel-ack to "-", as I see no need to do this.
Comment 10 John Mulligan 2020-02-27 15:24:32 UTC 
Upgrade playbook is in tech-preview state and will remain so. Due to resource constraints we will not be further improving or enhancing the upgrade playbook.