Description of problem: The upgrade playbook is to be used only while upgrading to the latest available OCS bits as suggested by Jose during 3.x downstream meeting. This should be documented in the upgrade playbook section of the Deployment guide. Version-Release number of selected component (if applicable): OCS 3.11 deployment guide How reproducible: OCS 3.11 Actual results: Upgrade performed using the upgrade playbook should only be to the latest available bits and this is not updated in the deployment guide doc. Expected results: Upgrade performed using the upgrade playbook should only be to the latest available bits and this should be updated in the deployment guide doc.
(In reply to Ashmitha Ambastha from comment #0) > Description of problem: > The upgrade playbook is to be used only while upgrading to the latest > available OCS bits as suggested by Jose during 3.x downstream meeting. This > should be documented in the upgrade playbook section of the Deployment guide. > > Version-Release number of selected component (if applicable): OCS 3.11 > deployment guide > Can this note be added in section 4.1. Specify Advanced Installer Variables https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index?lb_target=stage#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Specify_Advanced_variables As one of the notes in the end? let me know your thoughts here. I will update the note accordingly. > How reproducible: OCS 3.11 > > Actual results: Upgrade performed using the upgrade playbook should only be > to the latest available bits and this is not updated in the deployment guide > doc. > > Expected results: Upgrade performed using the upgrade playbook should only > be to the latest available bits and this should be updated in the deployment > guide doc.
Updated the content as Important in section 4.1. Specify Advanced Installer Variables https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index?lb_target=stage#chap-Documentation-Red_Hat_Gluster_Storage_Container_Native_with_OpenShift_Platform-Specify_Advanced_variables
Hello, Instead of having the note just in section 4.1, I would suggest having this in the upgrade playbook section as well. The user will be able to keep the note in mind while using the upgrade playbook. Having a point on upgrade playbook suddenly after a point on openshift-glusterfs/registry.yml, according to me, breaks the flow of the document. Also, in section 4.1, the important note about the upgrade playbook is incorrectly placed. The pointer before speaks of openshift-glusterfs/registry.yml playbook. IMPORTANT The upgrade playbook is to be used only while upgrading to the latest available OpenShift Container storage bits. There must not be a pre-existing registry in the OpenShift Container Platform cluster. @AnjanaKD, please reach out to me should you need any help. Moving this bug to failed QA.
https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/index?lb_target=preview#chap-upgrade_using_the_playbook Updated the content in chapter 7 Upgrading using the playbook
I see the content is now added in chapter 7 only. LGTM, moving the bug to verified. IMPORTANT The upgrade playbook is to be used only while upgrading to the latest available OpenShift Container Storage bits.