Description of problem: As of now in the docs i do not see a step to bring up heketi registry pods once they are down for glusterfs upgrade. We need to make sure that we add a note for the same. Doc URL : https://access.redhat.com/documentation/en-us/red_hat_openshift_container_storage/3.11/html-single/deployment_guide/ SectionName & Number : Needs to be added both in independent and converged mode sections. Suggestions for Improvement : Add a note asking the customer/user to bring back heketi registry pod which was brought down during glusterfs upgrade. Additional Info : Refer updating client on RedHat Openshift container platform nodes section for more info on how to bring back heketi pod.
Acking the bug for 3.11.3
Hello Bhavana, When we deploy OCP + OCS with both app & infra storge present, user needs to upgrade heketi & glusterfs pods in both the namespaces and scale them down in both namespaces. Hence having it in 6.2.3 may not be sufficient due to the fact that we do not have any note either in 6.2.3 or in the registry section asking customer to bring back their heketi registry pod. A note in one of the section would do it . Thanks kasturi