You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
test/extended/operators/operators: Rework "start all core operators"
Drop namespace from output strings, because ClusterOperator is
cluster-scoped [1].
Shift the 'available' variable down to the block of code that actually
consumes it, and convert it from a map to a counter, because we don't
care about displaying available operators.
Rename 'unavailable' to the more generic 'unready'. Also rephrase the
"still doing work" message to hinge on "ready", because "working" can
sound like "as expectd" not "still has stuff to do" [1]. An unready
operator may be available but progressing, etc., so 'unavailable' was
too specific.
Remove the 'break' from the wait-loop's ClusterOperator iteration.
The previous logic would only list the first unavailable operator.
With this commit we now list each unavailable operator while we wait.
Reformat the tab-writer block to print each operator and its worst
condition. The previous format had columns for progressing and
available, but none for degraded status. It also had a single message
column, making it unclear which condition's message was being
displayed. The new format displays the full type, status, reason, and
message of the worst condition for each operator.
The new code also includes the worst condition (or, if all existing
conditions for an operator were expected, any missing condition types)
in the failing error message. This should be more actionable with
less digging than the current messages, which just list the unsettled
operator names [2].
[1]: https://github.com/openshift/api/blob/b98a784d8e6dc93c416b40cdf54bf3102f2b61d2/config/v1/types_cluster_operator.go#L9
[2]: https://bugzilla.redhat.com/show_bug.cgi?id=1829405#c1
0 commit comments