Repository navigation
Commit 4910bc5
committed
test(e2e): wait for the opensearch handoff before the first API call
The first OpenSearch API call in the suite ran as soon as the data node
reported Ready. At that point the operator's bootstrap pod can still be
the elected cluster-manager, and until its own security configuration
loads it answers a cluster-manager action such as an index create with
503. The operator deletes the pod only after it has left the committed
voting configuration, so once the pod object is gone the cluster-manager
is the Ready data node.
The same Initialized flag that starts the handoff also releases a
rolling restart that can be pending since first boot, and with one
replica that restart takes the only node down. The step therefore also
waits for the StatefulSet to settle on its update revision.
Assisted-by: LLM
Signed-off-by: Aleksei Sviridkin <[email protected]>1 parent 564f540 commit 4910bc5
1 file changed
Lines changed: 27 additions & 0 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
197 | 197 | | |
198 | 198 | | |
199 | 199 | | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
| 203 | + | |
| 204 | + | |
| 205 | + | |
| 206 | + | |
| 207 | + | |
| 208 | + | |
| 209 | + | |
| 210 | + | |
| 211 | + | |
| 212 | + | |
| 213 | + | |
| 214 | + | |
| 215 | + | |
| 216 | + | |
| 217 | + | |
| 218 | + | |
| 219 | + | |
| 220 | + | |
| 221 | + | |
| 222 | + | |
| 223 | + | |
| 224 | + | |
| 225 | + | |
| 226 | + | |
200 | 227 | | |
201 | 228 | | |
202 | 229 | | |
| |||
0 commit comments