[Bug / Issue]: Manual Deployment does not succeed - Key vault has not been created whereas it exists-Unable to deploy

[jsporbert]

Jumpstart Solution

• Jumpstart ArcBox
• Jumpstart LocalBox
• Jumpstart Agora
• A specific Jumpstart scenario
• Jumpstart Drops
• Something else

What happened?

after validated the deployment I am unable to deploy. as it stated that the key vault does not exist but it does :(

We need a URL from you

https://jumpstart.azure.com/azure_jumpstart_localbox/manual_deployment

Deployment Method

Bicep

Relevant log output.

Code of Conduct and Licensing

• I agree to follow this project's Code of Conduct and Licensing terms.

[janegilring]

@jsporbert Did you configure this parameter to false, as you intend to perform the cluster deployment manually for learning purposes?

If you look at C:\LocalBox\azlocal.parameters.json, is it populated with values for your environment (e.g. keyVaultName)?
Could you share C:\LocalBox\Logs\New-LocalBoxCluster.log?

[jsporbert]

Yes ! Parameter is set to false !

here is the log

New-LocalBoxCluster.log

[janegilring]

Thanks, I will provision an instance with autoDeployClusterResource set to false and verify that the manual deployment works as expected and get back to you.

[janegilring]

@jsporbert I have now executed a deployment of LocalBox and performed the following manual steps in the portal:

1. Added and validated machines
2. Selected Create a new Key Vault

3. Verified that the Key Vault was present in the resource group
4. Configured networking based on the values in C:\LocalBox\azlocal.parameters.json

5. Configured management details based on the values in C:\LocalBox\azlocal.parameters.json

6. Left defaults on the Security tab

7. Selected this volume layout on the Advanced tab:

8. Resource creation on the Validation tab succeeded, so I went on and started validation:

9. The validation succeeded after some time

10. At the end the deployment was triggered:

This will likely take 2-3 hours to complete:

Based on the above, did you notice any differences from your environment or did you perform exactly the same steps?

If so, does the same thing happen if you start the cluster creation wizard from scratch?

[jsporbert]

I did not pursue with the portal installation as it should deploy everything from the templatte...

[janegilring]

I see, maybe I misunderstood - as based on the screenshot in the initial post it seemed to be the manual deployment experience triggered from here:

If you want to leverage the values from the template, the steps to follow would be the steps outlined here - which is using the Deploy a custom template option and copying the contents from C:\LocalBox\azlocal.json and C:\LocalBox\azlocal.parameters.json:

Are these the actions you performed?
If so, if you go to the LocalBox resource group and look at Deployments - are there any failures?

[jsporbert]

I did follow this and the template was successfully validated, when I click on teh deployment to 'deploy it' after validation I reached the Windows with the key vault error :)