@@ -90,13 +90,20 @@ Runtime changes are categorized as follows:
90
90
az networkcloud baremetalmachine list -g $CLUSTER_MRG --subscription $SUBSCRIPTION_ID --query "sort_by([].{name:name,kubernetesNodeName:kubernetesNodeName,location:location,readyState:readyState,provisioningState:provisioningState,detailedStatus:detailedStatus,detailedStatusMessage:detailedStatusMessage,cordonStatus:cordonStatus,powerState:powerState,kubernetesVersion:kubernetesVersion,machineClusterVersion:machineClusterVersion,machineRoles:machineRoles| join(', ', @),createdAt:systemData.createdAt}, &name)" -o table
91
91
```
92
92
93
- Validate the following resource states for each BMM:
93
+ Validate the following resource states for each BMM (except spare) :
94
94
- ReadyState: True
95
95
- ProvisioningState: Succeeded
96
96
- DetailedStatus: Provisioned
97
97
- CordonStatus: Uncordoned
98
98
- PowerState: On
99
99
100
+ One control-plane BMM is labeled as a spare with the following BMM status profile:
101
+ - ReadyState: False
102
+ - ProvisioningState: Succeeded
103
+ - DetailedStatus: Available
104
+ - CordonStatus: Uncordoned
105
+ - PowerState: Off
106
+
100
107
3 . Collect a profile of the tenant workloads:
101
108
```
102
109
az networkcloud clustermanager show -g $CM_RG --resource-name $CM_NAME --subscription $SUBSCRIPTION_ID -o table
@@ -219,7 +226,7 @@ az networkcloud baremetalmachine list -g $CLUSTER_MRG --subscription $SUBSCRIPTI
219
226
az networkcloud baremetalmachine list -g $CLUSTER_MRG --subscription $SUBSCRIPTION_ID --query "sort_by([].{name:name,kubernetesNodeName:kubernetesNodeName,location:location,readyState:readyState,provisioningState:provisioningState,detailedStatus:detailedStatus,detailedStatusMessage:detailedStatusMessage,cordonStatus:cordonStatus,powerState:powerState,kubernetesVersion:kubernetesVersion,machineClusterVersion:machineClusterVersion,machineRoles:machineRoles| join(', ', @),createdAt:systemData.createdAt}, &name)" -o table
220
227
```
221
228
222
- Validate the following states for each BMM:
229
+ Validate the following states for each BMM (except spare) :
223
230
- ReadyState: True
224
231
- ProvisioningState: Succeeded
225
232
- DetailedStatus: Provisioned
@@ -272,20 +279,15 @@ Run the following commands to check the status of the CM, Cluster, and BMM:
272
279
az networkcloud baremetalmachine list -g $CLUSTER_MRG --subscription $SUBSCRIPTION_ID --query "sort_by([].{name:name,kubernetesNodeName:kubernetesNodeName,location:location,readyState:readyState,provisioningState:provisioningState,detailedStatus:detailedStatus,detailedStatusMessage:detailedStatusMessage,cordonStatus:cordonStatus,powerState:powerState,kubernetesVersion:kubernetesVersion,machineClusterVersion:machineClusterVersion,machineRoles:machineRoles| join(', ', @),createdAt:systemData.createdAt}, &name)" -o table
273
280
```
274
281
275
- Validate the following resource states for each BMM:
282
+ Validate the following resource states for each BMM (except spare)
276
283
- ReadyState: True
277
284
- ProvisioningState: Succeeded
278
285
- DetailedStatus: Provisioned
279
286
- CordonStatus: Uncordoned
280
287
- PowerState: On
281
288
282
289
> [ !Note]
283
- > One control-plane BMM is labeled as a spare with the following BMM status profile:
284
- > - ReadyState: False
285
- > - ProvisioningState: Succeeded
286
- > - DetailedStatus: Available
287
- > - CordonStatus: Uncordoned
288
- > - PowerState: Off
290
+ > One control-plane BMM is labeled as a spare and is inactive.
289
291
290
292
4 . Collect a profile of the tenant workloads:
291
293
```
0 commit comments