Bug 1732140

Summary: Add a note saying "Upgrade playbook is only supported for ansible based converged Mode deployments"
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: RamaKasturi <knarra>
Component: cns-ansibleAssignee: John Mulligan <jmulligan>
Status: CLOSED CURRENTRELEASE QA Contact: Arun Kumar <arukumar>
Severity: medium Docs Contact:
Priority: unspecified    
Version: ocs-3.11CC: arukumar, dpivonka, hchiramm, kramdoss, madam, pasik, 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.11.153-1 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-02-13 05:22:09 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
Attaching the ansible logs. none

Description RamaKasturi 2019-07-22 19:17:31 UTC 
Description of problem:
Currently upgrade playbook is supported only on converged mode ansible based deployments. I think we should give out a important note to the customer when they invoke the upgrade playbook saying " Upgrade playbook is only supported for ansible based converged mode deployments" so that customer do not end up running this in any other mode of deployment accidentally.

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


How reproducible:


Steps to Reproduce:
1. 
2.
3.

Actual results:
Currently there is no Note which is being shown to the user when upgrade playbook is run.

Expected results:
An important note to the customer when they invoke the upgrade playbook saying " Upgrade playbook is only supported for ansible based converged mode deployments" 

Additional info:
Comment 8 RamaKasturi 2019-09-07 12:17:17 UTC 
Moving the bug to failed_qa state as i see that when upgrade playbook is executed it fails with error shown below.

PLAY [Set openshift_version for etcd, node, and master hosts] ***************************************************************************************************************
skipping: no hosts matched

PLAY [Verify Requirements] **************************************************************************************************************************************************

TASK [Gathering Facts] ******************************************************************************************************************************************************
ok: [dhcp47-87.lab.eng.blr.redhat.com]

TASK [Run variable sanity checks] *******************************************************************************************************************************************
fatal: [dhcp47-87.lab.eng.blr.redhat.com]: FAILED! => {"msg": "last_checked_host: dhcp46-167.lab.eng.blr.redhat.com, last_checked_var: ansible_python;'NoneType' object has n
o attribute '__getitem__'"}
        to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.retry

PLAY RECAP ******************************************************************************************************************************************************************
dhcp47-141.lab.eng.blr.redhat.com : ok=15   changed=0    unreachable=0    failed=0
dhcp47-87.lab.eng.blr.redhat.com : ok=43   changed=0    unreachable=0    failed=1   
localhost                  : ok=12   changed=0    unreachable=0    failed=0


INSTALLER STATUS ************************************************************************************************************************************************************
Initialization  : In Progress (0:00:41)

Inventory file options:
============================

# glusterfs
openshift_storage_glusterfs_timeout=900
openshift_storage_glusterfs_namespace=glusterfs
openshift_storage_glusterfs_storageclass=true
openshift_storage_glusterfs_storageclass_default=false
openshift_storage_glusterfs_block_storageclass=true
openshift_storage_glusterfs_block_storageclass_default=false
openshift_storage_glusterfs_block_deploy=true
openshift_storage_glusterfs_block_host_vol_create=true
openshift_storage_glusterfs_block_host_vol_size=100
openshift_storage_glusterfs_is_native=false
openshift_storage_glusterfs_heketi_is_native=true
openshift_storage_glusterfs_heketi_executor=ssh
openshift_storage_glusterfs_heketi_ssh_port=22
openshift_storage_glusterfs_heketi_ssh_user=root
openshift_storage_glusterfs_heketi_ssh_sudo=false
openshift_storage_glusterfs_heketi_ssh_keyfile="/root/.ssh/id_rsa"


Attaching ansible log file.
Comment 9 RamaKasturi 2019-09-07 12:19:09 UTC 
Created attachment 1612641 [details]
Attaching the ansible logs.
Comment 14 Daniel Pivonka 2019-10-07 19:07:05 UTC 
PR: https://github.com/openshift/openshift-ansible/pull/11939

This addresses the failed sanity checks for independent mode. Sanity checks should not run on independent gluster nodes.
Comment 15 Daniel Pivonka 2019-10-08 13:42:59 UTC 
PR Merged
Comment 16 Daniel Pivonka 2019-10-10 16:56:07 UTC 
fixed in version updated