ArcBox Full Data Services (CAPI) fails to deploy

[demond-hatter]

LogsBundle-bvc54k.zip

Is your issue related to a Jumpstart scenario, ArcBox, HCIBox, or Agora?
https://azurearcjumpstart.com/azure_jumpstart_arcbox/Full

Describe the issue or the bug

• ubuntuCAPIDeployment failed with error "Provisioning of VM extension installscript_CAPI has timed out. Extension provisioning has taken too long to complete. The extension last reported "Plugin enabled"

• Also, the Data services Logonscript fails because it is trying to pull the CAPI K8 Kubeconfig from a container that does not exist in the storage account "failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://arcboxopjkmqr7orhna.blob.core.windows.net/staging-capi

---

RESPONSE 403: 403 This request is not authorized to perform this operation using this resource type."

To Reproduce
see the submitted log bundle LogsBundle-bvc54k.zip

Expected behavior
Just trying to onboard the base scenario, including the data services components (MI and PostgresSql). Everything in the scenario seems to work except for the data services components.

Environment summary

Have you looked at the Troubleshooting and Logs section?

Screenshots

Additional context

[github-actions]

Hey friend! Thanks for opening this issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on the Azure Arc Jumpstart.

[sebassem]

@demond-hatter Thank you for raising this issue. Can you re-attach the log files? I don't see them in the issue for some reason.

[demond-hatter]

@sebassem Thanks for your assistance. I have edited my issue and attached the log bundle to it. For reference, I had already uploaded it to https://jumpstartsupport.blob.core.windows.net/logbundles per the instructions in the LogInstructions.txt file in the Arcbox/Logs folder.

Thanks again for your help.

[sebassem]

@demond-hatter Thanks for sharing the logs. I don't see the CAPI log, I think for some reason it didn't get added to the zip file. I couldn't reproduce the problem as my "full" deployment succeeded. I would suggest verifying the owner permission on the subscription and re-deploying a fresh one. If you see the same behavior please share the CAPI log to investigate further.

[demond-hatter]

@sebassem It seems the CAPI logs didn't get created because the container it is looking for (staging-capi) was never created. See excerpt below. I tried redeploying to a new resource group and got the exact same issue. What region did you deploy to? I'm deploying to Central US.

#####################################

- Downloading CAPI Install Logs

#####################################

INFO: Scanning...
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

failed to perform copy command due to error: cannot start job due to error: cannot list files due to reason GET https://
arcbox4xql2hwh7vt7w.blob.core.windows.net/staging-capi

RESPONSE 403: 403 This request is not authorized to perform this operation using this resource type.
ERROR CODE: AuthorizationResourceTypeMismatch

AuthorizationResourceTypeMismatchThis request is not
authorized to perform this operation using this resource type.
RequestId:19765307-701e-0038-4b31-40e134000000
Time:2024-01-05T23:49:10.7322434Z

[sebassem]

@demond-hatter Apologies for not being clear, you need to follow the troubleshooting guide to get the CAPI logs by sshing into the CAPI Vm. I deployed in Eastus and westeurope

[sebassem]

@demond-hatter Apologies for not being clear, you need to follow the troubleshooting guide to get the CAPI logs by sshing into the CAPI Vm. I deployed in Eastus and westeurope

@demond-hatter have you had a chance to check this guidance ?

[sebassem]

Closing this issue due to inactivity. @demond-hatter Please follow the guidance shared above and if you are still seeing issues, please re-open this issue or submit a new one