Upgrade fails due to unhealthy Ceph

Verify and repair Ceph object store health before upgrading Automation Suite on Linux.

Description

When trying to upgrade to a new Automation Suite version, you might see the following error message: Ceph objectstore is not completely healthy at the moment. Inner exception - Timeout waiting for all PGs to become active+clean.

Solution

To fix this upgrade issue, verify if the OSD pods are running and healthy by running the following command:

kubectl -n rook-ceph get pod -l app=rook-ceph-osd  --no-headers | grep -P '([0-9])/\1'  -v

• If the command does not output any pods, verify if Ceph placement groups (PGs) are recovering or not by running the following command:

  function is_ceph_pg_active_clean() {
    local return_code=1
    if kubectl -n rook-ceph exec  deploy/rook-ceph-tools -- ceph status --format json | jq '. as $root | ($root | .pgmap.num_pgs) as $total_pgs | try ( ($root | .pgmap.pgs_by_state[] | select(.state_name == "active+clean").count)  // 0) as $active_pgs | if $total_pgs == $active_pgs then true else false end' | grep -q 'true';then
      return_code=0
    fi
    [[ $return_code -eq 0 ]] && echo "All Ceph Placement groups(PG) are active+clean"
    if [[ $return_code -ne 0 ]]; then
      echo "All Ceph Placement groups(PG) are not active+clean. Please wait for PGs to become active+clean"
      kubectl -n rook-ceph exec deploy/rook-ceph-tools -- ceph pg dump --format json | jq -r '.pg_map.pg_stats[] | select(.state!="active+clean") | [.pgid, .state] | @tsv'
    fi
    return "${return_code}"
  }
  # Execute the function multiple times to get updated ceph PG status
  is_ceph_pg_active_clean
  

  Note:

  If none of the affected Ceph PG recovers even after waiting for more than 30 minutes, raise a ticket with UiPath® Support.

• If the command outputs pod(s), raise a ticket with UiPath® Support.