Bug 1660474 - glusterfs pods were not upgraded while using the upgrade playbook to upgrade from OCS 3.10 to OCS 3.11
Summary: glusterfs pods were not upgraded while using the upgrade playbook to upgrade ...
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
unspecified
urgent
Target Milestone: ---
: ---
Assignee: John Mulligan
QA Contact: Nitin Goyal
URL:
Whiteboard:
Depends On:
Blocks: 1644171 1703695
TreeView+ depends on / blocked
 
Reported: 2018-12-18 12:20 UTC by Ashmitha Ambastha
Modified: 2020-11-17 12:02 UTC (History)
11 users (show)

Fixed In Version: openshift-ansible-3.11.68-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-17 12:02:33 UTC
Embargoed:


Attachments (Terms of Use)

Description Ashmitha Ambastha 2018-12-18 12:20:36 UTC
Description of problem:

After running the upgrade playbook to upgrade OCS 3.10 to OCS 3.11 (latest available builds), the playbook passes.
But on validating the upgrade, it's seen that the glusterfs pods image version is still v3.10, not the version to which it was being upgraded to, i.e., 3.11.1-4
Please see the attachment for more details such as describe of the pods.

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

How reproducible: twice

Steps to Reproduce:
1. Create an OCP 3.11 + OCS 3.10 set up. Run constant block and file IOs.
2. Updated the inventory file parameters to the latest available OCS 3.11 builds. Ran the upgrade playbook, 
# ansible-playbook -i <inv_file> /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml 
3. The upgrade playbook passes. 
4. The validation of the upgrade fails as the glusterfs pods still show image version as v3.10. 

Actual results: Glusterfs pods were not upgraded. The image version shown is still v3.10

Expected results: Glusterfs pods should be upgraded. The image version shown should be v3.11.1-4

Comment 7 Saravanakumar 2019-01-24 07:24:59 UTC
Updated fixed in version


Note You need to log in before you can comment on or make changes to this bug.