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

Azure Kubernetes Service on Azure Stack HCI - connectK8 Guidance #2578

Closed
ddesonier opened this issue Jun 4, 2024 · 3 comments · Fixed by Azure/arc_jumpstart_docs#415
Closed
Assignees
Labels
documentation Improvements or additions to documentation HCIBox Jumpstart HCIBox related question Further information is requested

Comments

@ddesonier
Copy link

Is your feature request related to a new Jumpstart scenario you would like to contribute?

No

Is your feature request related to a problem? Please describe.

When deploying AKS as described in the Azure Kubernetes Service on Azure Stack HCI section, the command
az connectedk8s proxy -n hcibox-aks -g <name of your resource group>
resulted in an error in az cli
Failed to post access token to client proxyFailed to connect to MSI. Please make sure MSI is configured correctly. Get Token request returned: <Response [400]>
From Az Powershell the error was
The command failed with an unexpected error. Here is the traceback: Cannot load native module 'Crypto.Hash._MD5': Not found '_MD5.cp311-win_amd64.pyd', Cannot load '_MD5.pyd': cannot load library 'C:\Users\ddesonier\.azure\cliextensions\connectedk8s\Crypto\Util\..\Hash\_MD5.pyd': error 0xc1

Describe the solution you'd like.

This is easily resolved when updating connectedK8s
az extension update --name connectedk8s
Suggest adding a call out box or add to trouble shooting

Describe alternatives you've considered.

Additional context.

@dkirby-ms
Copy link
Contributor

Thank you for the feedback. We can consider updating the docs with additional troubleshooting in a future release.

@dkirby-ms dkirby-ms added the documentation Improvements or additions to documentation label Jun 4, 2024
@dkirby-ms dkirby-ms added the HCIBox Jumpstart HCIBox related label Jun 4, 2024
@likamrat likamrat added this to the July 2024 milestone Jul 1, 2024
@likamrat likamrat moved this to Triage needed in Azure Arc Jumpstart Jul 1, 2024
@likamrat likamrat moved this from Triage needed to In Progress in Azure Arc Jumpstart Jul 1, 2024
@likamrat
Copy link
Contributor

likamrat commented Jul 1, 2024

Re-open for future docs enhancement tracking

@likamrat likamrat reopened this Jul 1, 2024
@github-project-automation github-project-automation bot moved this from In Progress to Triage needed in Azure Arc Jumpstart Jul 1, 2024
@likamrat likamrat added the question Further information is requested label Jul 1, 2024
@likamrat likamrat moved this from Triage needed to In Progress in Azure Arc Jumpstart Aug 21, 2024
@likamrat likamrat modified the milestones: July 2024, August 2024 Aug 21, 2024
@likamrat likamrat modified the milestones: August 2024, September 2024 Sep 15, 2024
@ldabas-msft
Copy link
Contributor

Adding a callout in the docs to run az extension update --name connectedk8s before running connectedk8s

@ldabas-msft ldabas-msft linked a pull request Sep 30, 2024 that will close this issue
@github-project-automation github-project-automation bot moved this from In Progress to Done in Azure Arc Jumpstart Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation HCIBox Jumpstart HCIBox related question Further information is requested
Projects
Development

Successfully merging a pull request may close this issue.

4 participants