Description of problem: On OCS v3.10 cluster deployed using cns-deploy package the ansible upgrade playbook does not upgrade this env. I created a new inventory file and ran the playbook with appropriate server, volmanager and gluster-block images. Please see the ansible logs for more details. upgrade attempted from OCS cluster deployed using cns-deploy: # rpm -qa | grep cns-deploy cns-deploy-7.0.0-3.el7rhgs.x86_64 # rpm -qa | grep gluster glusterfs-client-xlators-3.12.2-18.el7rhgs.x86_64 glusterfs-cli-3.12.2-18.el7rhgs.x86_64 python2-gluster-3.12.2-18.el7rhgs.x86_64 glusterfs-geo-replication-3.12.2-18.el7rhgs.x86_64 glusterfs-libs-3.12.2-18.el7rhgs.x86_64 glusterfs-3.12.2-18.el7rhgs.x86_64 glusterfs-api-3.12.2-18.el7rhgs.x86_64 glusterfs-fuse-3.12.2-18.el7rhgs.x86_64 glusterfs-server-3.12.2-18.el7rhgs.x86_64 gluster-block-0.2.1-26.el7rhgs.x86_64 Images in the inventory file for upgrading: openshift_storage_glusterfs_image='registry.access.redhat.com/rhgs3/rhgs-server-rhel7:v3.11.2' openshift_storage_glusterfs_heketi_image='registry.access.redhat.com/rhgs3/rhgs-volmanager-rhel7:v3.11.2' openshift_storage_glusterfs_block_image='registry.access.redhat.com/rhgs3/rhgs-gluster-block-prov-rhel7:v3.11.2' How reproducible: always Steps to Reproduce: 1. Create a OCS 3.10 cluster using cns-deploy on an existing OCP cluster. 2. Create a new inventory file used to run the OCS ansible playbook. 3. Run the OCS upgrade playbook, ansible-playbook -i inv /usr/share/ansible/openshift-ansible/playbooks/openshift-glusterfs/upgrade.yml -vvv Actual results: The OCS upgrade fails with the playbook failing. Expected results: The upgrade playbook should be able to upgrade an OCS cluster deployed using cns-deploy
Created attachment 1552368 [details] ansible logs collected while running the upgrade playbook.
Status?
None at this time. Ashmitha, is this still seen? If so, can you provide the list of RPMs that should be installed, for reference?
Hello sarvana / Jose , Last comment i saw from Jose was that we are taking it in for now and we'll see. Are we taking this bug in for ocs3.11.4 ? Thanks kasturi
I'll say again, I don't know what the problem is. If you can provide me with a concrete problem I can tell you one way or another. As it stands, the upgrade playbook is ALREADY designed to upgrade cns-deploy clusters, so there should be no development work necessary. If you find a specific bug, let me know.
Hello ashmitha, Can you please provide the requested needinfo by Jose at the bug ? Thanks kasturi
Hello Humble, I did check in both the documents where we discussed about upgrade playbook queries but i do not see anything related to cns-deploy in both the documents. Attaching the documents for your reference. [1] https://docs.google.com/document/d/1dSfUOaL5h8ylzHZG45qRsDxYlMSuF57SoPkR1Yrnb0I/edit [2] https://docs.google.com/document/d/14YtAC7gi5U9GDExIo8EKD9l9XNIqSYRlxY9PjIRo7io/edit Thanks kasturi
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.