[ch5479] Ensure pgo test shows instances in "unknown" state #1118
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.
Checklist:
Type of Changes:
What is the current behavior? (link to any open issues here)
When a PostgreSQL instance is in an indeterminate state, e.g. during
initialization or when healing after a failover event, the type of
instance is unknown. However,
pgo test, and by extension the testendpoint in the
apiserver, were not returning the status of theinstances that were in this state.
What is the new behavior (if this is a feature change)?
This patch corrects this by allowing instances to have a type of
"unknown".
Issue: [ch5479]