Bug 1760404

Summary:	Upgrade playbook is failing at task create gluster block storage class
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Arun Kumar <arukumar>
Component:	cns-ansible	Assignee:	John Mulligan <jmulligan>
Status:	CLOSED WONTFIX	QA Contact:	Arun Kumar <arukumar>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	ocs-3.11	CC:	dpivonka, hchiramm, jmulligan, knarra, madam, rhs-bugs
Target Milestone:	---	Keywords:	Reopened
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:19:19 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 Arun Kumar 2019-10-10 13:17:37 UTC

Description of problem:
Upgrade Playbook is failing at TASK [openshift_storage_glusterfs : Create Gluster Block 

the snippet of  ansible logs:
=============================
2019-10-10 11:23:59,884 p=20923 u=ec2-user |  TASK [openshift_storage_glusterfs : Create Gluster Block StorageClass] ******************************************************************************************************
2019-10-10 11:23:59,884 p=20923 u=ec2-user |  task path: /usr/share/ansible/openshift-ansible/roles/openshift_storage_glusterfs/tasks/glusterblock_storageclass.yml:19
2019-10-10 11:24:00,074 p=20923 u=ec2-user |  Using module file /usr/share/ansible/openshift-ansible/roles/lib_openshift/library/oc_obj.py
2019-10-10 11:24:00,295 p=20923 u=ec2-user |  Escalation succeeded
2019-10-10 11:24:00,920 p=20923 u=ec2-user |  The full traceback is:
  File "/tmp/ansible_Lp0743/ansible_module_oc_obj.py", line 47, in <module>


ansible version:
================
 rpm -qa|grep openshift-ansible
openshift-ansible-roles-3.11.152-1.git.0.3e13655.el7.noarch
openshift-ansible-3.11.152-1.git.0.3e13655.el7.noarch
openshift-ansible-playbooks-3.11.152-1.git.0.3e13655.el7.noarch
openshift-ansible-docs-3.11.152-1.git.0.3e13655.el7.noarch
openshift-ansible-test-3.11.152-1.git.0.3e13655.el7.noarch


I will attach the ansible logs and inventory file shortly.

Comment 5 Arun Kumar 2019-10-21 14:34:57 UTC

I am reopening this bug because it is hit only on AWS setup.
With respect to comment 3, I tested this bug on VMware setup as referred in comment 4, the issue is not seen in vmvawe setup. so I closed this bug.
But I was upgrading in aws setup with openshift-ansible 153-1 and openshift-ansible 153-2, it is reproducible.
I tried it 3/3 so  I am able to reproduce it.

It will attach the logs and inventory file for more info.

Comment 8 RamaKasturi 2019-10-22 05:59:19 UTC

Hello John,

  I am okay moving this bug out of 3.11.4 release but it would be good to provide a workaround for the customer in case he hits the issue and document this as a known issue.

Thanks
kasturi

Comment 10 John Mulligan 2020-02-27 15:19:19 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.