Skip to content

Commit d1d5ebd

Browse files
Merge pull request #298693 from matternst7258/matternst7258/replace-on
[operator-nexus] Add precondition for replace to power on machine
2 parents 397d799 + 3a40e51 commit d1d5ebd

File tree

1 file changed

+2
-1
lines changed

1 file changed

+2
-1
lines changed

articles/operator-nexus/howto-bare-metal-best-practices.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Best practices for Bare Metal Machine operations
33
description: Steps that should be taken before executing any Bare Metal Machine replace, or reimage actions. Highlight essential prerequisites and common pitfalls to avoid.
4-
ms.date: 04/17/2025
4+
ms.date: 04/23/2025
55
ms.topic: how-to
66
ms.service: azure-operator-nexus
77
ms.custom: template-how-to, best-practices
@@ -176,6 +176,7 @@ Before initiating any `replace` operation, ensure the following preconditions ar
176176
- Perform high level checks covered in the article [Troubleshoot Bare Metal Machine Provisioning].
177177
- Evaluate any Bare Metal Machine warnings or degraded conditions which could indicate the need to resolve hardware, network, or server configuration problems before a `replace` operation.
178178
For more information, see [Troubleshoot Degraded Status Errors on Bare Metal Machines] and [Troubleshoot Bare Metal Machine Warning Status].
179+
- Validate Bare Metal Machine has been powered on.
179180
- Validate that there are no running firmware upgrade jobs.
180181
Follow steps in section [Determine if Firmware Update Jobs are Running](#determine-if-firmware-update-jobs-are-running).
181182

0 commit comments

Comments
 (0)