Bug 1696635

Summary: OCS upgrade playbook does not upgrade OCS cluster deployed using cns-deploy
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Ashmitha Ambastha <asambast>
Component: cns-ansibleAssignee: John Mulligan <jmulligan>
Status: CLOSED WONTFIX QA Contact: Ashmitha Ambastha <asambast>
Severity: high Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: hchiramm, jarrpa, jmulligan, knarra, kramdoss, madam, pprakash, rhs-bugs, rtalur, sarumuga
Target Milestone: ---Keywords: ZStream
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:16:26 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    
Attachments:
Description Flags
ansible logs collected while running the upgrade playbook. none

Description Ashmitha Ambastha 2019-04-05 10:30:03 UTC 
Description of problem:
On OCS v3.10 cluster deployed using cns-deploy package the ansible upgrade playbook does not upgrade this env. I created a new inventory file and ran the playbook with appropriate server, volmanager and gluster-block images. 
Please see the ansible logs for more details. 

upgrade attempted from OCS cluster deployed using cns-deploy: 

# rpm -qa  | grep cns-deploy
cns-deploy-7.0.0-3.el7rhgs.x86_64

# rpm -qa | grep gluster
glusterfs-client-xlators-3.12.2-18.el7rhgs.x86_64
glusterfs-cli-3.12.2-18.el7rhgs.x86_64
python2-gluster-3.12.2-18.el7rhgs.x86_64
glusterfs-geo-replication-3.12.2-18.el7rhgs.x86_64
glusterfs-libs-3.12.2-18.el7rhgs.x86_64
glusterfs-3.12.2-18.el7rhgs.x86_64
glusterfs-api-3.12.2-18.el7rhgs.x86_64
glusterfs-fuse-3.12.2-18.el7rhgs.x86_64
glusterfs-server-3.12.2-18.el7rhgs.x86_64
gluster-block-0.2.1-26.el7rhgs.x86_64

Images in the inventory file for upgrading: 

openshift_storage_glusterfs_image='registry.access.redhat.com/rhgs3/rhgs-server-rhel7:v3.11.2'

openshift_storage_glusterfs_heketi_image='registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7:v3.11.2'

openshift_storage_glusterfs_block_image='registry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7:v3.11.2'


How reproducible: always


Steps to Reproduce:
1. Create a OCS 3.10 cluster using cns-deploy on an existing OCP cluster.
2. Create a new inventory file used to run the OCS ansible playbook.
3. Run the OCS upgrade playbook, 
 
 ansible-playbook -i inv /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml  -vvv
 

Actual results: The OCS upgrade fails with the playbook failing.  


Expected results: The upgrade playbook should be able to upgrade an OCS cluster deployed using cns-deploy
Comment 2 Ashmitha Ambastha 2019-04-05 10:39:02 UTC 
Created attachment 1552368 [details]
ansible logs collected while running the upgrade playbook.
Comment 4 Yaniv Kaul 2019-04-14 14:23:35 UTC 
Status?
Comment 6 Jose A. Rivera 2019-04-15 13:36:09 UTC 
None at this time.

Ashmitha, is this still seen? If so, can you provide the list of RPMs that should be installed, for reference?
Comment 9 RamaKasturi 2019-07-02 17:40:46 UTC 
Hello sarvana / Jose ,

   Last comment i saw from Jose was that we are taking it in for now and we'll see. Are we taking this bug in for ocs3.11.4 ?

Thanks
kasturi
Comment 10 Jose A. Rivera 2019-07-02 17:44:57 UTC 
I'll say again, I don't know what the problem is. If you can provide me with a concrete problem I can tell you one way or another. As it stands, the upgrade playbook is ALREADY designed to upgrade cns-deploy clusters, so there should be no development work necessary. If you find a specific bug, let me know.
Comment 13 RamaKasturi 2019-07-03 08:42:28 UTC 
Hello ashmitha,

   Can you please provide the requested needinfo by Jose at the bug ?

Thanks
kasturi
Comment 18 RamaKasturi 2019-07-10 14:10:22 UTC 
Hello Humble,

   I did check in both the documents where we discussed about upgrade playbook queries but i do not see anything related to cns-deploy in both the documents. Attaching the documents for your reference.

[1] https://docs.google.com/document/d/1dSfUOaL5h8ylzHZG45qRsDxYlMSuF57SoPkR1Yrnb0I/edit

[2] https://docs.google.com/document/d/14YtAC7gi5U9GDExIo8EKD9l9XNIqSYRlxY9PjIRo7io/edit

Thanks
kasturi
Comment 23 John Mulligan 2020-02-27 15:16:26 UTC 
Upgrade playbook is in tech-preview state and will remain so. Due to resource constraints we will not be futher improving or enhancing the upgrade playbook.