Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HCI cluster deployment failed but validation passed. #2411

Closed
hungry1526 opened this issue Feb 10, 2024 · 3 comments
Closed

HCI cluster deployment failed but validation passed. #2411

hungry1526 opened this issue Feb 10, 2024 · 3 comments
Assignees
Labels
HCIBox Jumpstart HCIBox related upstream related Related to non-Jumpstart, Azure upstream product issue or a feature

Comments

@hungry1526
Copy link

hungry1526 commented Feb 10, 2024

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?

HCIBox

Describe the issue or the bug

HCI Cluster ARM template is validated but deployment failed. It timed out on "Deploy Arc infrastructure components". Where can I find more log? The error from the portal seems vague and it may be related to service principal but I never configure this parameter. How can I find more logs?

To Reproduce

It failed on this step:
image

Error from portal:
Type 'DeployArb' of Role 'MocArb' raised an exception: Exception while installing ARB in step [DeployArb:Doing AZ Login using service principal] AZ Login using SP failed after 15 retries. Aborting Arb deployment - Error = at at DeployArbInternal, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2311.0.30\content\Scripts\MocArbHelper.psm1: line 1124 at DeployArb, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2311.0.30\content\Scripts\MocArbLifeCycleManager.psm1: line 127 at , C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 127 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 123 Command Arguments ------- --------- DeployArbInternal {Parameters=CloudEngine.Configurations.EceInterfaceParameters} {} {CloudEngine.Configurations.EceInterfaceParameters, MocArb, DeployArb, C:\NugetStore\Micr... Invoke-EceInterfaceInternal {CloudDeploymentModulePath=C:\NugetStore\Microsoft.AzureStack.Solution.Deploy.CloudDeploy... at Trace-Error, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2311.0.30\content\Scripts\Common\Tracer.psm1: line 63 at DeployArbInternal, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2311.0.30\content\Scripts\MocArbHelper.psm1: line 1402 at DeployArb, C:\NugetStore\Microsoft.AzureStack.MocArb.LifeCycle.1.2311.0.30\content\Scripts\MocArbLifeCycleManager.psm1: line 127 at , C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 127 at Invoke-EceInterfaceInternal, C:\CloudDeployment\ECEngine\InvokeInterfaceInternal.psm1: line 123

Expected behavior

Environment summary

I am using AZD on east us.

Have you looked at the Troubleshooting and Logs section?

Screenshots

Additional context

@hungry1526 hungry1526 added the triage issue or feature up for triage label Feb 10, 2024
@dkirby-ms
Copy link
Contributor

Is it possible you can redeploy the environment? This looks like its possibly something upstream related in ARB deployment process but hard to say for sure.

@dkirby-ms dkirby-ms added HCIBox Jumpstart HCIBox related and removed triage issue or feature up for triage labels Feb 12, 2024
@dkirby-ms dkirby-ms self-assigned this Feb 12, 2024
@hungry1526
Copy link
Author

Hey Dale, thanks for the response. I tried it twice; the failing step and the error is the same.

@dkirby-ms
Copy link
Contributor

I tried reproducing this and am not able to. Having said that, we pushed an updated build this morning that uses the latest HCI OS 2311.2 build. I would suggest completely tearing down the environment and redeploy from scratch.

@likamrat likamrat added the upstream related Related to non-Jumpstart, Azure upstream product issue or a feature label Mar 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
HCIBox Jumpstart HCIBox related upstream related Related to non-Jumpstart, Azure upstream product issue or a feature
Projects
Development

No branches or pull requests

3 participants