Failed to apply artifact #1 - how to check failure reason

Category: azure devtest labs


wibble2000 on Mon, 26 Sep 2016 01:42:56

I was trying to create a Linux VM basing on a customized base image(using New-AzureRmResourceGroupDeployment), the VM was created successfully but the following artifact installing failed.

1. Where can I find detailed failure logs for root cause?

2. I guess the artifact installation failure is due to incorrect VM login info - installing artifact requires root password, but I didn't find any place to pass root password to it(I am using ARM). Should I pass root(or admin on windows) password to VM creation process? where?



AshokPeddakotla-MSFT on Mon, 26 Sep 2016 14:10:44


Thank you for posting on the azure forums!

You can use two options available to see the failed artifacts error logs information.

Please check the blog post on How to troubleshoot failing Artifacts in AzureDevTestLabs for more details.

Also, refer the article to Create custom artifacts for your DevTest Labs VM and Add a Git artifact repository to a lab in Azure DevTest Labs incase if you are trying to install custom artifacts.

You may want to see the available artifacts in Git.

Hope this helps.





When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer so that other customers can benefit from it.

David R. Williamson (MSFT) on Thu, 13 Oct 2016 22:16:39

Hi -

We've recently improved the artifacts status and result experience. We now show each of the artifacts ever applied to the virtual machine (since the feature was created) along with various information like the repo from which the artifact was used, the install date/time, and the deployment message.

To find this, open the Lab VM blade and look for a menu item named Artifacts. While the artifacts are installing, a message shows up on the Lab VM blade about the progress which is clickable and takes you to the same place.

In order to apply artifacts to a VM, DevTest Labs does not use your local admin credentials (those are never stored, simply passed to the Compute Resource Provider when the VM is being created). Rather it has permission to the VM as a resource in Azure and uses VM extensions to perform the work. The only exception to this is some of the scripts (namely chocolatey) need a local admin account to run, so one is temporarily created for the duration of the script, and subsequently removed.