SBE update fails at the Invoke SBE CAU Scan stage

Question

SBE update fails at the Invoke SBE CAU Scan stage

L, Lisha (PSD-GCC) 0

we are currently facing a failure during the SBE update on the affected Azure Local cluster.

The update is failing at the Invoke SBE CAU Scan stage, and we do not see an SBE log folder being created. This suggests that the process is failing before it reaches the HPE portion of the SBE update.

The affected nodes are HPE ProLiant Gen12 Premiere Solutions.

We have also run the Send-DiagnosticData command on the cluster and shared the diagnostic data with the Microsoft team for further investigation.

We are currently waiting for an engineer from the Pacific Time Zone to be assigned to this case so that they can join the customer call and help troubleshoot the issue.

It has been more than 24 hours, so I just wanted to check if there is an estimated timeline for the engineer assignment, or how much longer we may need to wait.

We would appreciate any update you can provide.

0 comments

1 answer

Your answer

Answer 1

Hi Lisha,

For an Azure Local SBE update that fails specifically at Invoke SBE CAU Scan, the next step is to inspect the UpdateRun and CAU health-check results rather than wait for the SBE log folder. Microsoft documents that each update stage creates an UpdateRun, which can be queried with:

Get-SolutionUpdateRun

Also check the SBE state:

$Update = Get-SolutionUpdateEnvironment
$Update | ft SbeFamily, HardwareModel, CurrentSbeVersion, State

For the failed update, retrieve the health-check details:

Get-SolutionUpdate -Id <SolutionUpdateResourceId> |
    Format-List Version, State, HealthCheckResult

Microsoft's troubleshooting guidance specifically uses these results to identify failures before or during the CAU phase.

Because this is an HPE ProLiant Gen12 system, also verify that the installed HPE SBE version is the one supported for the Azure Local version you are updating to. Microsoft maintains the validated HPE SBE combinations in the SBE documentation.

If Invoke SBE CAU Scan fails before SBE execution and the health checks show a CAU failure, resolve that CAU condition first; the absence of an SBE log directory is then expected because the HPE portion has not started yet.