Description of problem: Changes in the documentation that should be made: https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/3/html/installation_guide_for_red_hat_enterprise_linux/upgrading-a-red-hat-ceph-storage-cluster "In the rolling_update.yml playbook, change the health_osd_check_retries and health_osd_check_delay values to 40 and 30 respectively. health_osd_check_retries: 40 health_osd_check_delay: 30" The above is already the default in the rolling_update.yml playbook. The line that reads: "Create new copies of the group_vars/all.yml.sample and group_vars/osds.yml.sample named group_vars/all.yml and group_vars/osds.yml respectively and edit them according to you deployment. Skip this step when upgrading from version 3.x to the latest version. For details, see Appendix H, Changes in Ansible Variables Between Version 2 and 3 and Section 3.2, “Installing a Red Hat Ceph Storage Cluster” ." It was significantly easier to make the appropriate changes in the variables from version to 2 and 3 then copying the new sample files (all.yml.sample and osds.yml.sample) and re-add everything back in. I just wanted to point that out. The section that comments out the #mdss portion that is under IMPORTANT section, I believe should be moved into the prerequisites section. The final ceph -s , it should show a status example. My ceph version that I updated to: 12.2.4-10
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. Regards, Giri
Level setting the severity of this defect to "High" with a bulk update. Pls refine it to a more closure value, as defined by the severity definition in https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity
'"In the rolling_update.yml playbook, change the health_osd_check_retries and health_osd_check_delay values to 40 and 30 respectively. health_osd_check_retries: 40 health_osd_check_delay: 30" The above is already the default in the rolling_update.yml playbook.' This is now 50/30. I assume it is correct. "It was significantly easier to make the appropriate changes in the variables from version to 2 and 3 then copying the new sample files" Safest way to ensure you have the right new variables is to start with them and move over customizations, even if it's slower. "The section that comments out the #mdss portion that is under IMPORTANT section, I believe should be moved into the prerequisites section. " That seems reasonable. Will do.