Harden scratch setup third-party readiness probes
This commit is contained in:
@@ -57,7 +57,7 @@ dotnet run --project src/Cli/StellaOps.Cli/StellaOps.Cli.csproj -- `
|
||||
|
||||
| Output | Class | Meaning | Action |
|
||||
|---|---|---|---|
|
||||
| `health=starting` (RustFS) | Warning | Service still warming up | Wait and recheck `docker compose ... ps` |
|
||||
| `GET http://127.1.1.3:8333/` returns `403` | Info | SeaweedFS S3 endpoint is live and rejecting anonymous root requests | Treat `403` as ready for the scratch setup smoke |
|
||||
| `SM remote service probe failed (localhost:56080)` | Warning | Optional SM remote provider is unavailable | Ignore unless validating China SM remote crypto profile |
|
||||
| `stellaops-dev-rekor restarting` without `--profile sigstore` | Warning | Optional Sigstore container from prior run | Ignore for default profile or remove stale container |
|
||||
| `policy ... scheduler_exceptions_tenant_isolation already exists` | Blocking | Outdated Scheduler migration idempotency | Update code and rerun seeding |
|
||||
@@ -158,6 +158,12 @@ psql -h db.stella-ops.local -U stellaops -d stellaops_dev -c "SELECT 1"
|
||||
|
||||
# Valkey
|
||||
valkey-cli -h cache.stella-ops.local ping
|
||||
|
||||
# SeaweedFS S3 root returns 403 when unauthenticated; that still proves readiness
|
||||
curl -I http://s3.stella-ops.local/
|
||||
|
||||
# Zot OCI registry
|
||||
curl -I http://registry.stella-ops.local/v2/
|
||||
```
|
||||
|
||||
Infrastructure versions (from `docker-compose.dev.yml`):
|
||||
|
||||
Reference in New Issue
Block a user