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
The Live status should appear neutral, however it appears yellow in 21.1.5
To Reproduce
Note: I haven't been able to reproduce it on roachprod (v21.1.5 clusters), but Michael did report seeing this happen when stopping a node on the cluster, getting it into the Suspect state (yellow), and then restart it again.
We aggreagate rows for multiregion cluster in nodes list
table and used single method to calculate status badge for
aggregated and single node row. After adding additional
node status `NODE_STATUS_DRAINING` we have got
enum values overlap and that lead to `LIVE` badge with
`warning` color.
To fix that, and avoid same problem in future, changes for
splitting up aggregated and non aggregated color values
were made.
Resolves: cockroachdb#67274
Release note(ui): fix color mismatch of node status badge
on cluster overview page.
68049: ui: cluster overview node status color mismatch r=elkmaster a=elkmaster
We aggreagate rows for multiregion cluster in nodes list
table and used single method to calculate status badge for
aggregated and single node row. After adding additional
node status `NODE_STATUS_DRAINING` we have got
enum values overlap and that lead to `LIVE` badge with
`warning` color.
To fix that, and avoid same problem in future, changes for
splitting up aggregated and non aggregated color values
were made.
Resolves: #67274
Release note(ui); fix color mismatch of node status badge
on cluster overview page.
Co-authored-by: Vlad Los <[email protected]>
Identified by @mikeczabator
Describe the problem
The
Live
status should appear neutral, however it appears yellow in 21.1.5To Reproduce
Note: I haven't been able to reproduce it on roachprod (v21.1.5 clusters), but Michael did report seeing this happen when stopping a node on the cluster, getting it into the
Suspect
state (yellow), and then restart it again.Epic CRDB-8313
The text was updated successfully, but these errors were encountered: