Let the provisioning dump say why it is empty - #257
Open
vitramir wants to merge 1 commit into
Open
Conversation
Every command in the dump ended in 2>/dev/null, so a namespace with nothing in it and a cluster kubectl cannot reach print the same nothing. Both are what the last week of failures look like, and the step that exists to tell them apart discarded the answer. It now asks whether the cluster answers before asking what is in it, and prints the organization the readiness wait blocks on. That object is baked into the image rather than provisioned at boot, so 'the platform is provisioning its organization' means the baked state is not there, not that something is still running.
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.
E2E has failed on every repo since 2026-08-09 with:
and the diagnostic that exists to explain it prints:
Every command in that step ended in
2>/dev/null, so an empty namespace and an unreachable cluster produce identical output. Both match what we see, and there is no way to tell which from the log.This keeps stderr, and asks whether the cluster answers (
cluster-info,get nodes,get ns) before asking what is insideagyn-platform.It also prints the
systemOrganization. That object is baked into the image, not provisioned at boot — a VM created today and one created two days ago report the samecreationTimestampand the sameorganizationId, because both come from the image. So the CLI's "provisioning its organization" is misleading: the field is blank because the baked state is not there, not because something is still working.No behaviour change outside the
if: failure()block.