azure-sdk-for-java: Identity e2e tests for running fail in Azure VM MSI

Describe the issue: Test the Testing azure-identity in Azure VM MSI with instructions (Repro steps). When run the MSI test, it displays the error :

The maven default version is 3.6.0 in VM. We also tried to upgrade the Maven version, but it is complex, we didn’t achieve the expected result.

Environment: Env: Azure VM Package: https://search.maven.org/artifact/com.azure/azure-identity/1.7.0-beta.2/jar Related issue: https://github.com/Azure/azure-sdk/issues/815

Expected behavior: Run the MSI test can pass.

@josefree for notification.

About this issue

Original URL
State: closed
Created 2 years ago
Comments: 15 (10 by maintainers)

Most upvoted comments

@v-jiaodi I’ll get the update done. Thanks for letting me know it worked.

billwert on Nov 4, 2022

@v-jiaodi

I merged a PR to unblock the test setup. Can you run the cloudshell test again from source code on main branch ?

This is the output I see for Cloudshell tests: Screen Shot 2022-11-02 at 1 42 12 PM

If you still see same issue, then follow updated instructions here for cloudshell testing. https://github.com/Azure/azure-sdk/issues/795#issuecomment-559900596

Can you also try Web jobs with updated source code ?

Thank you.

g2vinay on Nov 3, 2022

@v-jiaodi Here’s some updated instructions.

The failure you got and shared with me in IM last night was due to a project changed that happened at some point in the pom file. It isn’t automatically building dependencies now. To fix that, we’ll build the dependencies after the clone but before running the test:

 echo -e `az vm run-command invoke \
    --ids /subscriptions/{subscription}/resourceGroups/$RESOURCE_GROUP/providers/Microsoft.Compute/virtualMachines/{vm} \
    --command-id RunShellScript \
    --scripts "cd /tmp/azure-sdk-for-java && export AZURE_VAULT_URL=https://$KEY_VAULT_NAME.vault.azure.net && mvn install -pl sdk/identity/azure-identity,sdk/core/azure-core,sdk/core/azure-core-http-netty,sdk/keyvault/azure-security-keyvault-keys,sdk/keyvault/azure-security-keyvault-secrets,sdk/keyvault/azure-security-keyvault-certificates,sdk/core/azure-core-test -T 1 -f pom.xml -Dgpg.skip -Dmaven.javadoc.skip -Drevapi.skip -DskipSpringITs -DskipTests -Dspotbugs.skip -Djacoco.skip -am -DfailIfNoTests=false" \                                                                                                                   -o json \
    --query "value[0].message"`

Then we can run the test (for example the system assigned):

echo -e `az vm run-command invoke \
    --ids /subscriptions/{subscription}/resourceGroups/$RESOURCE_GROUP/providers/Microsoft.Compute/virtualMachines/{vm} \
    --command-id RunShellScript \
    --scripts "cd /tmp/azure-sdk-for-java/sdk/e2e && export AZURE_VAULT_URL=https://$KEY_VAULT_NAME.vault.azure.net && mvn test -Dtest=ManagedIdentityCredentialLiveTest#testIMDSEndpointWithSystemAssigned*  -f pom.xml -Dgpg.skip -am -DfailIfNoTests=false" \                                                                                                                                                                      -o json \
    --query "value[0].message"`

Note the changes to the test command line: removal of -am, changed directory to include sdk/e2e, removal of -pl sdk/e2e.

With these changes I was able to successfully get a passing test with no changes to the code in main branch. You can go back to using azure/azure-sdk-for-java instead of any fork.

I’ll consult with folks to figure out how we fix this going forward but this should unblock you for now. Thank you for your help!

billwert on Nov 3, 2022