Azure local deployment failed during Cluster Creation? How to troubleshoot this issue?

Question

Azure local deployment failed during Cluster Creation? How to troubleshoot this issue?

PROZAR 16

I am getting the following error, how to troubleshoot Storage Spaces Direct issues, when I see the logs file C:\Windows\temp\StorageClusterValidationReport-2025-06-20.16-55-08 it only says it failed. But how to fix those dependencies, I didnt find any documentation. Please help me with the below error.

Exception

Type 'ConfigCluster' of Role 'Cluster' raised an exception: Cluster Validation failed in following tests: Name Value ---- ----- Storage Spaces Direct {List All Disks for Storage Spaces Direct, List File Shares, List Storage Enclosures, ... . Review the StorageClusterValidation report C:\Windows\temp\StorageClusterValidationReport-2025-06-20.16-55-08 available under C:\Windows\Cluster\Reports on the server for details. Command Arguments ------- --------- Test-StorageCluster {Parameters=CloudEngine.Configurations.EceInterfaceParameters, ClusterShortName=XXX-HCICLU} {} <ScriptBlock> {CloudEngine.Configurations.EceInterfaceParameters, Cluster, ConfigCluster, C:\NugetStore... Invoke-EceInterfaceInternal {CloudDeploymentModulePath=C:\NugetStore\Microsoft.AzureStack.Solution.Deploy.CloudDeploy... <ScriptBlock> {CloudEngine.Configurations.EceInterfaceParameters, bb00efe8-2e27-41a6-88ab-c6d237a48a7c,... at Trace-Error, C:\NugetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.10.2502.0.1013\content\CloudDeployment\Common\Tracer.psm1: line 63 at Test-StorageCluster, C:\NugetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.10.2502.0.1013\content\CloudDeployment\Classes\Storage\StorageHelpers.psm1: line 493 at ConfigCluster, C:\NugetStore\Microsoft.AzureStack.Fabric.Storage.SCPSModule.10.2502.0.1013\content\CloudDeployment\Classes\Cluster\Cluster.psm1: line 182 at <ScriptBlock>, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 139 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 134 at <ScriptBlock>, <No file>: line 36

Anusree Nashetty 4,375 Reputation points Microsoft External Staff Moderator

2025-06-24T19:46:05.4+00:00

Hi PROZAR,

Did you get a chance to see the response provided by Jerald Felix. If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.
Anusree Nashetty 4,375 Reputation points Microsoft External Staff Moderator

2025-06-27T23:32:58.99+00:00

Hi PROZAR,

The HTTP error 12152 during WinRM operations indicates a proxy configuration issue where internal traffic is not correctly bypassing the proxy.

Your environment shows $env:https_proxy is set to http://localhost:40343 while your machine-wide HTTPS_PROXY is set to http://XX.XX.XX.XX:8080This inconsistency suggests a proxy configuration conflict.
WinRM may need explicit proxy bypass configuration. Configure WinRM to bypass proxy for local addresses.
The error suggests possible SSL/TLS negotiation problems. Ensure proper certificates are configured.
If you're using older versions of Windows Server, install all latest updates. There is a known issue HTTP 12152 WSMan error caused by WMI failures.

1 answer

Your answer

Anusree Nashetty 4,375 Reputation points Microsoft External Staff Moderator

2025-06-24T19:46:05.4+00:00

Hi PROZAR,

Did you get a chance to see the response provided by Jerald Felix. If you have any further queries, let me know. If the information is helpful, please click on Upvote and Accept Answer on it.
Anusree Nashetty 4,375 Reputation points Microsoft External Staff Moderator

2025-06-27T23:32:58.99+00:00

Hi PROZAR,

The HTTP error 12152 during WinRM operations indicates a proxy configuration issue where internal traffic is not correctly bypassing the proxy.

Your environment shows $env:https_proxy is set to http://localhost:40343 while your machine-wide HTTPS_PROXY is set to http://XX.XX.XX.XX:8080This inconsistency suggests a proxy configuration conflict.
WinRM may need explicit proxy bypass configuration. Configure WinRM to bypass proxy for local addresses.
The error suggests possible SSL/TLS negotiation problems. Ensure proper certificates are configured.
If you're using older versions of Windows Server, install all latest updates. There is a known issue HTTP 12152 WSMan error caused by WMI failures.

Answer 1

Hi PROZAR,

The error you’re seeing indicates that the Storage Spaces Direct (S2D) validation tests failed during your local cluster deployment:

Cluster Validation failed in following tests: Storage Spaces Direct {List All Disks…, List File Shares…, List Storage Enclosures…}

Below I have listed down the various approach to solve this issue:

Review the Validation Report

Check the detailed cluster validation report generated at:

makefile

C:\Windows\Cluster\Reports\StorageClusterValidationReport-2025-06-20.16-55-08.html

Open it in a browser and look for failures under:

List All Disks
List File Shares
List Storage Enclosures

These sections will pinpoint exactly which check(s) failed.

Common Causes & Fixes

a) Disk Configuration Issues

Ensure each disk is unformatted, online, and not part of a RAID/partition.

S2D requires raw disks. Use Disk Management or Get-PhysicalDisk in PowerShell to verify.

b) Missing or Incompatible Storage Enclosures

For JBODs or DAS, ensure controllers are supported by S2D.

Verify connectivity and correct enclosure IDs with Get-StorageEnclosure.

c) Network & SMB Settings

Check your cluster's management/data networks are healthy and properly configured.

Ensure SMB bindings are enabled (Get-SmbServerNetworkInterface) and assigned correctly.

d) Firmware or Driver Mismatches

Use vendor tools to confirm consistent, supported firmware/drivers across all nodes.
Inconsistent versions often cause validation failures.

Re-Run the Validation Tests

After correcting the above issues, run in powershell:
Test-Cluster –Include "Storage Spaces Direct"

You should see all tests Pass before you attempt to retry deployment.

I hope it helps to solve it. Kindly check and share your feedback.

Best Regards,

Jerald Felix

PROZAR 16 Reputation points

2025-06-25T10:36:06.51+00:00

An error occurred while executing the test. One or more errors occurred. There was an error retrieving information about the Disks from node '{0}'. ERROR CODE : 0x80131500; NATIVE ERROR CODE : 1. WS-Management cannot process the request. The operation failed because of an HTTP error. The HTTP error (12152) is: The server returned an invalid or unrecognized response .

I am getting the above error on the validation report generated. However when we are checking WinRM and PS Remote we are able to connect other systems. Also we have provided the bypass list for all internal traffic on the proxy. Still we are getting this issue.

Here is the environment variables:

[Environment]::SetEnvironmentVariable("HTTPS_PROXY", "http://XX.XX.XX.XX:8080", "Machine")

$env:HTTPS_PROXY = [System.Environment]::GetEnvironmentVariable("HTTPS_PROXY", "Machine")

[Environment]::SetEnvironmentVariable("HTTP_PROXY", "http://XX.XX.XX.XX:8080","Machine")

$env:HTTP_PROXY = [System.Environment]::GetEnvironmentVariable("HTTP_PROXY", "Machine")

$no_proxy=localhost,127.0.0.1,Node-01,Node-02,CLU-01,.svc,kubernetes.default.svc,.svc.cluster.local,10.XX.0.0./16,172.XX.0.0/12,192.168.0.0/16,192.168.X.0/24,169.254.0.0/16"

[Environment]::SetEnvironmentVariable("NO_PROXY", $no_proxy, "Machine")

$env:NO_PROXY = [System.Environment]::GetEnvironmentVariable("NO_PROXY", "Machine")

PS C:\Users\Administrator> echo "https :" $env:https_proxy "http :" $env:http_proxy "bypasslist " $env:no_proxy

https :

http://localhost:40343

http :

http://XX.XX.XX.XX:8080

bypasslist

localhost,127.0.0.1,Node-01,Node-02,CLU-01,.svc,10.XX.XXX.XX,10.XX.XXX.XX,10.XX.XXX.XX,10.XX.XXX.XX,169.254.0.0/16,0.0.0.0,10.0.0.0/8,172.16.0.0/12,192.168.0.0/16

Share via

Azure local deployment failed during Cluster Creation? How to troubleshoot this issue?

1 answer

Your answer