omnigraph-bootstrap-rehearsal
checks.x86_64-linux.omnigraph-bootstrap-rehearsal
· build #994
· raw
1--- s3: state found, marker present2omnigraph-cluster-bootstrap: cluster state and marker s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized present; nothing to do3--- s3: state found, marker absent4omnigraph-cluster-bootstrap: cluster state present without a marker; adopted s3://rehearsal/clusters/dev-graph/ and wrote s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized5--- s3: state missing, marker absent6omnigraph-cluster-bootstrap: no cluster state and no marker: initializing s3://rehearsal/clusters/dev-graph/7omnigraph-cluster-bootstrap: initialized s3://rehearsal/clusters/dev-graph/ and wrote s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized8--- s3: state missing, marker present9omnigraph-cluster-bootstrap: REFUSING TO INITIALIZE s3://rehearsal/clusters/dev-graph/10The marker s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized exists, so this storage root was initialized before,11but it no longer holds cluster state (__cluster/state.json): the root was12lost or emptied. Applying now would create a new, empty cluster in its13place, so nothing was applied.14Restore the root from backup, then: systemctl restart omnigraph-cluster-bootstrap15To deliberately start over with an empty cluster, delete the marker16s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized and then: systemctl restart omnigraph-cluster-bootstrap17--- s3: apply fails18omnigraph-cluster-bootstrap: no cluster state and no marker: initializing s3://rehearsal/clusters/dev-graph/19omnigraph-cluster-bootstrap: initializing s3://rehearsal/clusters/dev-graph/ failed; the marker s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized was not written, so the next start retries20--- s3: status fails21{"ok":false,"diagnostics":[{"severity":"error","code":"state_read_error"}]}22omnigraph-cluster-bootstrap: omnigraph cluster status failed for s3://rehearsal/clusters/dev-graph/; nothing was applied23--- local: state found, marker present24omnigraph-cluster-bootstrap: cluster state and marker store/_omnigraph-markers/root.initialized present; nothing to do25--- local: state found, marker absent26omnigraph-cluster-bootstrap: cluster state present without a marker; adopted store/root/ and wrote store/_omnigraph-markers/root.initialized27--- local: state missing, marker absent28omnigraph-cluster-bootstrap: no cluster state and no marker: initializing store/root/29omnigraph-cluster-bootstrap: initialized store/root/ and wrote store/_omnigraph-markers/root.initialized30--- local: state missing, marker present31omnigraph-cluster-bootstrap: REFUSING TO INITIALIZE store/root/32The marker store/_omnigraph-markers/root.initialized exists, so this storage root was initialized before,33but it no longer holds cluster state (__cluster/state.json): the root was34lost or emptied. Applying now would create a new, empty cluster in its35place, so nothing was applied.36Restore the root from backup, then: systemctl restart omnigraph-cluster-bootstrap37To deliberately start over with an empty cluster, delete the marker38store/_omnigraph-markers/root.initialized and then: systemctl restart omnigraph-cluster-bootstrap39--- local: apply fails40omnigraph-cluster-bootstrap: no cluster state and no marker: initializing store/root/41omnigraph-cluster-bootstrap: initializing store/root/ failed; the marker store/_omnigraph-markers/root.initialized was not written, so the next start retries42--- local: status fails43{"ok":false,"diagnostics":[{"severity":"error","code":"state_read_error"}]}44omnigraph-cluster-bootstrap: omnigraph cluster status failed for store/root/; nothing was applied45--- s3: HEAD answers 50046omnigraph-cluster-bootstrap: HEAD http://127.0.0.1:32871/rehearsal/clusters/_omnigraph-markers/dev-graph.initialized for the marker s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized answered HTTP 500; cannot tell whether the root was initialized, nothing was applied47--- s3: endpoint from AWS_ENDPOINT_URL48omnigraph-cluster-bootstrap: cluster state present without a marker; adopted s3://rehearsal/clusters/dev-graph/ and wrote s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized49--- s3: endpoint unset50omnigraph-cluster-bootstrap: cannot read the marker s3://rehearsal/clusters/_omnigraph-markers/dev-graph.initialized: s3_endpoint is unset (the endpoint comes from AWS_ENDPOINT_URL_S3 or AWS_ENDPOINT_URL); nothing was applied51--- rejected root s3 bucket52omnigraph-cluster-bootstrap: the storage root s3://rehearsal/ has no basename after stripping trailing slashes, so it has no parent to hold its marker; nothing was applied53--- rejected root slash54omnigraph-cluster-bootstrap: the storage root / has no basename after stripping trailing slashes, so it has no parent to hold its marker; nothing was applied55--- rejected root gs56omnigraph-cluster-bootstrap: unsupported storage scheme in gs://rehearsal/root; only s3://, file:// and plain paths are supported; nothing was applied57--- every S3 request is path-style and SigV4-signed for the configured key and region