Bug 1705988

Summary:	OCS upgrade playbook has to be supported for all OCP versions
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Ashmitha Ambastha <asambast>
Component:	cns-ansible	Assignee:	John Mulligan <jmulligan>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ashmitha Ambastha <asambast>
Severity:	urgent	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	arukumar, dpivonka, hchiramm, jarrpa, jmulligan, knarra, kramdoss, madam, puebele, rhs-bugs, rtalur, sarumuga
Target Milestone:	---	Keywords:	ZStream
Target Release:	OCS 3.11.z Batch Update 4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	openshift-ansible-3.10.174-1	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-13 05:22:20 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 Ashmitha Ambastha 2019-05-03 11:04:18 UTC

Description of problem:
When upgrading OCP 3.10 + OCS 3.10 cluster to OCP 3.10 + OCS 3.11, to access the upgrade playbook, it's required to upgrade the openshift-ansible version to latest (in this case, update from 3.10 to 3.11) 

Openshift-ansible should be backported to all previous OCP versions. 

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


How reproducible:


Steps to Reproduce:
1. Deploy a cluster of OCP 3.10+ OCS 3.10.
2. To upgrade this cluster, upgrade openshift-ansible to 3.11. 
3. To avoid compatibility issues, with latest openshift ansible on an older ocp cluster, we should backport upgrade playbook fix to all ocp versions.

Comment 2 Ashmitha Ambastha 2019-05-03 11:30:27 UTC

During the 3.x downstream meeting on 2nd May, Jose has taken the AI to speak with openshift-ansible team and resolve this issue. Adding a needinfo on him to update with the resolution.

Comment 3 Jose A. Rivera 2019-05-03 19:34:14 UTC

Okay, sounds like we'll need to backport the playbook to openshift-ansible 3.10. That's the only over OCP version supported, so we should be good to go there.

Comment 16 Daniel Pivonka 2019-09-16 18:16:32 UTC

Removing upgrade playbook

PR: https://github.com/openshift/openshift-ansible/pull/11906

Comment 17 Arun Kumar 2019-09-26 06:36:07 UTC

Hi,

Based on comment 14 and commnet 16 I have verified that there is no playbook with name upgrade.yml under /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/

[root@master openshift-glusterfs]# ansible-playbook -i ~/inv /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml
ERROR! the playbook: /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml could not be found

[root@master openshift-glusterfs]# ls /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml
ls: cannot access /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml: No such file or directory

Comment 18 Arun Kumar 2019-09-26 06:39:03 UTC

With respect to comment 17 
versions:
[root@master openshift-glusterfs]# rpm -qa|grep ansible
openshift-ansible-roles-3.10.174-1.git.0.74b0837.el7.noarch
ansible-2.4.6.0-1.el7ae.noarch
openshift-ansible-playbooks-3.10.174-1.git.0.74b0837.el7.noarch
openshift-ansible-3.10.174-1.git.0.74b0837.el7.noarch
openshift-ansible-docs-3.10.174-1.git.0.74b0837.el7.noarch