Bug 1754760 - Upgrade playbook does not update the image tag inside the ds while upgrading the gluster pods on an AWS cluster
Summary: Upgrade playbook does not update the image tag inside the ds while upgrading ...
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
high
high
Target Milestone: ---
: OCS 3.11.z Batch Update 4
Assignee: John Mulligan
QA Contact: Arun Kumar
URL:
Whiteboard:
Depends On:
Blocks: 1703695
TreeView+ depends on / blocked
 
Reported: 2019-09-24 04:08 UTC by Arun Kumar
Modified: 2020-02-13 05:21 UTC (History)
6 users (show)

Fixed In Version: openshift-ansible-3.11.152-1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-02-13 05:21:56 UTC
Embargoed:

Attachments (Terms of Use)

Comment 3 Daniel Pivonka 2019-10-01 16:49:59 UTC 
Based on the log provided the task 'Delete glusterfs daemonset w/o cascade' failed to delete the old daemon set. This failure did not fail the playbook though.

'Failed connect to localhost:8443; Connection refused'

Later in the playbook task 'Deploy GlusterFS pods' should have deployed the upgraded daemon set but was skipped because the old daemon set still existed. 


To fix this I propose a check after the task 'Delete glusterfs daemonset w/o cascade' to make sure the daemon set was actually deleted if not fail the playbook.
Comment 4 Daniel Pivonka 2019-10-02 15:10:07 UTC 
PR: https://github.com/openshift/openshift-ansible/pull/11932
Comment 7 Daniel Pivonka 2019-10-04 18:35:51 UTC 
PR: https://github.com/openshift/openshift-ansible/pull/11936

This will allow daemonset deletes to succeed if the default openshift rest api port is not used. In the inventory provided it was changed to port 443 using the var openshift_master_api_port.
Comment 8 Daniel Pivonka 2019-10-07 14:23:25 UTC 
PR merged and fixed in version updated
Note You need to log in before you can comment on or make changes to this bug.