Skip to content

[Bug / Issue]: Heartbeat from nested VMs not landing in Azure Arc #3322

@lmiroslaw

Description

@lmiroslaw

Jumpstart Solution

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

What happened?

Solution: JumpStart - ArcBox, bicep based deployment

Issue: VMs under HyperV cannot sent heartbeat message to Azure Arc. Error message is that the tenantID does not exist although that's not the case. Also Credentials

See `DeploymentStatus.log

Name : Azure Arc Connected Machine is connected
Path : {, Azure Arc Connected Machine is connected}
Data :
ExpandedName : Azure Arc Connected Machine is connected
ExpandedPath : ArcBox-Ubuntu-01.Azure Arc Connected Machine is connected
Result : Failed
ErrorRecord : {Expected 'Connected', but got $null.}`

We need a URL from you

https://jumpstart.azure.com/azure_jumpstart_arcbox/ITPro

Deployment Method

Bicep

Relevant log output.

and `level=fatal msg="error connecting machine to Azure: failed to send a heartbeat: [certStore] ClientAssertionCredential authentication failed.  --------------------------------------------------------------------------------\nRESPONSE]--------------------------------------------------------------------------------/nRESPONSE) 400: 400 Bad Request\n--------------------------------------------------------------------------------\n{\n  \"error\": \"invalid_tenant\",\n  \"error_description\": \"AADSTS90002: Tenant 'XXX' not found. Check to make sure you have the correct tenant ID and are signing into the correct cloud. Check with your subscription administrator, this may happen if there are no active subscriptions for the tenant. (...)   \"error_uri\": \"https://login.microsoftonline.com/error?code=90002\"\n}\n--------------------------------------------------------------------------------\n\n[certFile] error acquiring token from certificate: ClientCertificateCredential authentication failed.`

Code of Conduct and Licensing

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

Metadata

Metadata

Assignees

Labels

Bug-IssueIt either shouldn't be doing this or needs an investigationNeeds-AttentionThis work item needs to be reviewed by a member of the core team

Type

Projects

Status

No status

Relationships

None yet

Development

No branches or pull requests

Issue actions