omnigraph-readiness-rehearsal
checks.x86_64-linux.omnigraph-readiness-rehearsal
· build #994
· raw
1--- dead MAINPID fails fast without polling2omnigraph-server exited during startup before serving; see `journalctl -u omnigraph-server`. A fresh or never-applied storage root needs `systemctl restart omnigraph-cluster-apply` (or the bootstrap unit) before the server can start.3elapsed 0s, requests: 04--- served equals expected with a live MAINPID is ready5elapsed 0s, requests: 16--- served below expected fails fast7omnigraph-server serves 1 of 2 declared graphs. Graphs are opened only at startup, so waiting will not help: run `systemctl restart omnigraph-cluster-apply` (or the bootstrap unit) to apply them, then restart omnigraph-server.8elapsed 0s, requests: 19--- a quarantined graph fails fast10omnigraph-server quarantined 1 graph(s) during startup and will not serve them until it restarts; see `journalctl -u omnigraph-server` ('graph quarantined during startup' lines) and `omnigraph-cluster status`.11elapsed 0s, requests: 112--- no expected count accepts zero served graphs13elapsed 0s, requests: 114--- 503 then 200 is transient15elapsed 4s, requests: 316--- 200 that is not a readiness report fails fast17omnigraph-server answered http://omnigraph.rehearsal.invalid:8090/readyz with a body that is not a readiness report: {}18elapsed 0s, requests: 119--- 200 with ready false keeps polling, then times out20omnigraph-server did not answer http://omnigraph.rehearsal.invalid:8090/readyz within 3 seconds21elapsed 4s, requests: 422--- never ready within the timeout fails with the timeout message23omnigraph-server did not answer http://omnigraph.rehearsal.invalid:8090/readyz within 3 seconds24curl: (22) The requested URL returned error: 50325elapsed 3s, requests: 3