Skip to content

Commit 30b71c0

Browse files
authored
Update howto-cluster-runtime-upgrade-template.md
Fix for merge comments.
1 parent 7c27df4 commit 30b71c0

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

articles/operator-nexus/howto-cluster-runtime-upgrade-template.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -172,7 +172,7 @@ az networkcloud cluster show -n $CLUSTER_NAME -g $CLUSTER_RG --subscription $SUB
172172
}
173173
```
174174

175-
### Running Cluster upgrade with `PauseAfterRack` Strategy
175+
### How to run Cluster upgrade with `PauseAfterRack` Strategy
176176

177177
`PauseAferRack` strategy allows the customer to control the upgrade by requiring an API call to continue to the next Rack after each Compute Rack completes to the configured threshold.
178178

@@ -235,14 +235,14 @@ Add a Tag to the BMM resource to track any BMM that fails to complete provisioni
235235
|BF provision issue |<DE_ID> |
236236
```
237237

238-
## Continuing upgrade during `PauseAfterRack` strategy:
238+
## How to continue upgrade during `PauseAfterRack` strategy
239239
Once a compute Rack meets the success threshold, the upgrade pauses until the user signals to the operator to continue the upgrade.
240240

241241
Use the following command to continue upgrade once a Compute Rack is paused after meeting the deployment threshold for the Rack:
242242
```
243243
az networkcloud cluster continue-update-version -g $CLUSTER_RG -n $CLUSTER_NAME$ --subscription $SUBSCRIPTION_ID
244244
```
245-
## Troubleshooting Cluster and BMM upgrade failures.
245+
## How to troubleshoot Cluster and BMM upgrade failures.
246246
The following troubleshooting documents can help recover BMM upgrade issues:
247247
- [Hardware validation failures](troubleshoot-hardware-validation-failure.md)
248248
- [BMM Provisioning issues](troubleshoot-bare-metal-machine-provisioning.md)

0 commit comments

Comments
 (0)