ci: dump OpenBao pod labels, Service endpoints and server logs on system-test failure#1986
Merged
Merged
Conversation
…tem-test failure Every system test today failed with the whole vault seeding chain (ClusterSecretStore, PushSecrets, vault-config Job) timing out on 'dial tcp <openbao-active ClusterIP>:8200: connect: no route to host' — a ClusterIP with zero backends. The existing diagnose step dumps neither pod labels (the openbao-active=true label that service registration must set), nor Service endpoints, nor the OpenBao server log, so the post-mortem could not tell WHY the active Service was empty. Add an 'OpenBao state' group with all three. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Jun 10, 2026
Merged
Contributor
|
🎉 This PR is included in version 1.47.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every system test today (all six remediation PRs and the unrelated Renovate PRs #1971/#1972/#1974, and the tenant-DNS PR run at 19:24) fails identically: the
infrastructureKustomization times out on the 21 resources of the vault seeding chain, all erroring withi.e. the
openbao-activeService has zero backends in the test cluster —openbao-0is initialized and unsealed (the vault-config init container confirms it), yet never carries theopenbao-active=truelabel that OpenBao's Kubernetes service registration must set. This started with today's openbao active-service cutover (#1964/#1965/#1907) and is pre-existing on main, not caused by the open PRs.The existing 🩺 diagnose step dumps neither pod labels, nor Service endpoints, nor the OpenBao server log — the three facts needed to pin why the label is missing. This PR adds an "OpenBao state" group with all three; its own system-test run on this PR will produce the first actionable dump.
Validation
🤖 Generated with Claude Code