Ryotaro Banno e9c1f81d79 ci: wait for all OSD pods to become Running in wait_for_prepare_pod ...

Currently, `wait_for_prepare_pod` only waits until 1 prepare pod and 1
OSD pod are in Running state.

So if `wait_for_ceph_to_be_ready` failed after `wait_for_prepare_pod`
succeeded, there are 4 possible cases:

1. some prepare pods didn't start correctly;
2. some prepare pods didn't finish correctly;
3. some OSD pods didn't start correctly; or
4. all prepare pods and OSD pods worked correctly, but some other
   process failed.

As far as I understand, the number of prepare pods on the GitHub CI is
always 1, so cases 1 and 2 are not problematic. However, it is hard to
distinguish the other two cases from the CI log.

To solve the above problems, this patch makes wait_for_prepare_pod wait
for all OSD pods to become running state. If wait_for_prepare_pod
timeouts before the OSD pods become running state, this will be a strong
indication that the OSD pods didn't start properly (i.e., case 3).

Signed-off-by: Ryotaro Banno <ryotaro.banno@gmail.com>

2023-12-25 05:12:30 +00:00

..

framework

ci: remove ceph SVGs in helm test

2023-12-19 17:05:21 +05:30

integration

core: remove webhook & controller-runtime from apis

2023-12-01 14:15:40 +05:30

manifests

core: update default image to ceph v17.2.6

2023-04-11 14:07:11 -06:00

scripts

ci: wait for all OSD pods to become Running in wait_for_prepare_pod

2023-12-25 05:12:30 +00:00

.gitignore

tests: refactor integration tests

2017-06-29 15:20:28 -07:00

ceph-status-out

core: change directory layout

2021-11-30 09:12:53 +01:00