Azure-docs: AADLoginForLinux doesn't install on B1ls VM size running Ubuntu

Created on 23 Sep 2019  Ā·  7Comments  Ā·  Source: MicrosoftDocs/azure-docs

I tried many times but the extension won't install on a VM with B1ls size running Ubuntu Image..The install runs forever and shows as 'unavailable' in the Portal. Can this doc be updated if this particular size can't be used for this extension? Thanks.


Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com āžŸ GitHub issue linking.

Pri2 cxp product-question triaged virtual-machines-linusvc

Most helpful comment

We did some debugging and this is what we found:

  • Calling ā€œapt-get updateā€ takes very long time probably because of limited resources. As a result the agent kills the installation script and using the extension consistently fails.
  • Running the installation script manually may succeed but we were also seeing random failures, again caused by the limited resources. For example, trying to install the standard package apt-transport-https failed with ā€œFATAL -> Failed to forkā€.

There are too may repos registered with apt. Maybe we don’t need http://azure.archive.com/ubuntu and removing it from the image will improve the situation; I don’t know. The aadloing package is pretty small and if the script manages to finish, the AAD Login will work.

For now, the only workaround I can think of is this:

  1. Try to use extension
  2. Go to the machine and run ā€œapt-cache policy ā€œ grep ā€˜packages.microsoft.comā€™ā€. If it shows up, the script has made it to the part where it installs this repo. If not, we have to provide some instructions how to manually add the repo.
  3. Run ā€œapt-get install aadloginā€

All 7 comments

@jits2019 the extension does not have a VM size requirement. Likely there is a different issue.

What version of Ubuntu are you running? Have you tried it on the same image using another VM size?

I have tried with latest ubuntu and other ones too..other VM size works with same image..also other OS works on same vm size..issue is only with B1ls + Ubuntu

hmm strange.

@yyanev @SanDeo-MSFT is this expected?

Also pinging @ayshakeen in case this has come up before on B1s

We did some debugging and this is what we found:

  • Calling ā€œapt-get updateā€ takes very long time probably because of limited resources. As a result the agent kills the installation script and using the extension consistently fails.
  • Running the installation script manually may succeed but we were also seeing random failures, again caused by the limited resources. For example, trying to install the standard package apt-transport-https failed with ā€œFATAL -> Failed to forkā€.

There are too may repos registered with apt. Maybe we don’t need http://azure.archive.com/ubuntu and removing it from the image will improve the situation; I don’t know. The aadloing package is pretty small and if the script manages to finish, the AAD Login will work.

For now, the only workaround I can think of is this:

  1. Try to use extension
  2. Go to the machine and run ā€œapt-cache policy ā€œ grep ā€˜packages.microsoft.comā€™ā€. If it shows up, the script has made it to the part where it installs this repo. If not, we have to provide some instructions how to manually add the repo.
  3. Run ā€œapt-get install aadloginā€

Thanks @yyanev !

@jits2019 you can go ahead and give the work arounds a try. All in all, seems to be based on limited resources of that specific series.

We won't add that info to the document at this time but you comment will remain on the doc so if other users encounter the same problem they will be able to see the work around. If we have enough users running into this issue and trying it on this size we can always reopen and consider adding it to the documentation.

Added a note that if you are installing this extension on a previously created VM it should be allocated with at least 1GB of memory for the install to succeed.

Was this page helpful?
0 / 5 - 0 ratings