Bug 1705900 - upgrade playbook to support upgrade of 2 gluster clusters managed by 1 heketi
Summary: upgrade playbook to support upgrade of 2 gluster clusters managed by 1 heketi
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: cns-ansible
Version: ocs-3.11
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: John Mulligan
QA Contact: Ashmitha Ambastha
URL:
Whiteboard:
Depends On:
Blocks: 1703695
TreeView+ depends on / blocked
 
Reported: 2019-05-03 07:49 UTC by Ashmitha Ambastha
Modified: 2020-02-13 05:22 UTC (History)
10 users (show)

Fixed In Version: openshift-ansible-3.11.115
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-13 05:22:00 UTC
Embargoed:
sarumuga: needinfo-

Attachments (Terms of Use)

Description Ashmitha Ambastha 2019-05-03 07:49:54 UTC 
Description of problem:
------------------------
In a cluster where 2 gluster clusters are managed by 1 heketi pod, the upgrade playbook is not supported and flow of the upgrade is not understood. 

Upgrade should be supported in such deployment scenarios. Upgrade of two gluster clusters should take place separately with risk to data integrity to the existing cluster. 

Version-Release number of selected component (if applicable): during upgrades from OCS 3.10 to OCS 3.11 
 

Steps to Reproduce:
1. Deploy a cluster of 2 gluster clusters managed by 1 heketi pod in version OCP 3.11 + OCS 3.10
2. Update inventory file to latest available bits, eg : v3.11.2
3. Run upgrade playbook to upgrade this cluster to OCP 3.11 + OCS 3.11.2

Actual results:Not supported. 
Expected results: Upgrade should be supported for such deployments.
Comment 2 Jose A. Rivera 2019-05-03 19:16:33 UTC 
Valid, taking this in.
Comment 3 Jose A. Rivera 2019-05-07 14:45:56 UTC 
PR is upstream: https://github.com/openshift/openshift-ansible/pull/11588
Comment 4 Jose A. Rivera 2019-05-08 14:04:39 UTC 
PR is merged.
Note You need to log in before you can comment on or make changes to this bug.