Hello Azure Local Community,
We are experiencing a serious update orchestration issue on our production Azure Local cluster.
Environment:
- 3-node Dell Azure Local cluster
Current installed version: 12.2609.1003.7
Target update: 12.2610.1004.50 (2026.10 Feature Update)
Dell SBE: 5.0.2609.1715
Production Hyper-V workloads
Problem:
The update repeatedly reaches 85% completion, fails, and automatically starts another attempt without administrator intervention.
We have observed four solution update runs: three failed and one reported as InProgress.
Each retry can trigger Cluster-Aware Updating (CAU), causing node drains, VM migrations and reboots during business hours.
We attempted to disable the CAU clustered role:
Disable-CauClusterRole
The role was successfully disabled and reported Offline. However, Azure Local subsequently brought it back Online and continued the update process.
Additional findings:
CAU reported failed to complete failback successfully on one node.
Another node experienced an ECE RemoteTask orchestration timeout on TCP port 8888.
The Azure Local Action Plan showed Run PostUpdateScript as InProgress.
CAU reported Found leftover state from a previous Updating Run.
The automated Azure Local diagnostic suggested a possible update orchestration retry/concurrency loop.
All three nodes subsequently returned to Up, and ECEAgent services were Running.
One production VM temporarily entered a Failed/Saved state before recovering.
Multiple solution update Run IDs were observed, although actual concurrent execution has not been conclusively verified.
Our main question:
Is there a Microsoft-supported way to safely pause or stop the Azure Local update orchestrator and prevent further automatic CAU retries, node drains and reboots until a scheduled maintenance window?
We do not want to forcibly terminate PowerShell processes, stop ECEAgent or manually remove orchestration state.
We would also appreciate guidance on resolving the repeated failure at 85% and safely resuming the update later.
This is a production environment, and preventing unexpected VM downtime during business hours is our highest priority.
Thank you for your assistance.Hello Azure Local Community,
We are experiencing a serious update orchestration issue on our production Azure Local cluster.
Environment:
3-node Dell Azure Local cluster
Current installed version: 12.2609.1003.7
Target update: 12.2610.1004.50 (2026.10 Feature Update)
Dell SBE: 5.0.2609.1715
Production Hyper-V workloads
Problem:
The update repeatedly reaches 85% completion, fails, and automatically starts another attempt without administrator intervention.
We have observed four solution update runs: three failed and one reported as InProgress.
Each retry can trigger Cluster-Aware Updating (CAU), causing node drains, VM migrations and reboots during business hours.
We attempted to disable the CAU clustered role:
Disable-CauClusterRole
The role was successfully disabled and reported Offline. However, Azure Local subsequently brought it back Online and continued the update process.
Additional findings:
CAU reported failed to complete failback successfully on one node.
Another node experienced an ECE RemoteTask orchestration timeout on TCP port 8888.
The Azure Local Action Plan showed Run PostUpdateScript as InProgress.
CAU reported Found leftover state from a previous Updating Run.
The automated Azure Local diagnostic suggested a possible update orchestration retry/concurrency loop.
All three nodes subsequently returned to Up, and ECEAgent services were Running.
One production VM temporarily entered a Failed/Saved state before recovering.
Multiple solution update Run IDs were observed, although actual concurrent execution has not been conclusively verified.
Our main question:
Is there a Microsoft-supported way to safely pause or stop the Azure Local update orchestrator and prevent further automatic CAU retries, node drains and reboots until a scheduled maintenance window?
We do not want to forcibly terminate PowerShell processes, stop ECEAgent or manually remove orchestration state.
We would also appreciate guidance on resolving the repeated failure at 85% and safely resuming the update later.
This is a production environment, and preventing unexpected VM downtime during business hours is our highest priority.
Thank you for your assistance.