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
Copy file name to clipboardExpand all lines: articles/operator-nexus/troubleshoot-bare-metal-machine-degraded.md
+6-29Lines changed: 6 additions & 29 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -43,39 +43,16 @@ az networkcloud baremetalmachine list -g <ResourceGroup_Name> --output table --
43
43
44
44
**Example Azure CLI output**
45
45
46
+
This example shows a deployment with two currently degraded BMMs (`compute01` and `compute04`), and two cordoned BMMs (`compute02` and `compute04`). Not all degraded BMMs are cordoned (yet), and not all of the healthy BMMs are uncordoned (yet) - due to the fixed delay before automatic cordoning and uncordoning takes effect.
47
+
46
48
```
47
49
Name PowerState ProvisioningState ReadyState CordonStatus DetailedStatus DetailedStatusMessage
0 commit comments