yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #75949
[Bug 1803173] Re: cloud-init disables user on azure at second reboot
Hi.
I added a 'linux' package task here. It seems that in bug 1551419 patches were added
to the ubuntu kernel to do the right thing. Possibly those patches were inadvertantly
dropped? Either way, it seems like the [Ubuntu] kernel should promise this consistently
so that multiple consumers do not need to all know about this issue and handle it
themselves.
That said, we will fix cloud-init to handle it.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1803173
Title:
cloud-init disables user on azure at second reboot
Status in cloud-init:
Confirmed
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hello,
Environment:
platform: Azure
arm image: Canonical UbuntuServer 16.04-DAILY-LTS latest
Steps:
Deploy VM with user/pass authentication
Install latest linux-next-upstream kernel (for example 4.19.0-4db9d11bcbef, where 4db9d11bcbef is the git tag from the linux-next latest tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/next/linux-next/)
reboot (all good)
reboot again
cloud-init disables the username password authentication
I checked the cloud-init logs and found:
2018-11-01 16:45:28,566 - init.py[INFO]: User already exists, skipping.
2018-11-01 16:45:28,570 - util.py[DEBUG]: Running command ['passwd', '-l', ''] with allowed return codes [0] (shell=False, capture=True)
2018-11-01 16:45:28,793 - util.py[DEBUG]: Reading from /etc/sudoers (quiet=False)
2018-11-01 16:45:28,795 - util.py[DEBUG]: Read 781 bytes from /etc/sudoers
2018-11-01 16:45:28,796 - util.py[DEBUG]: Writing to /etc/sudoers.d/90-cloud-init-users - ab: [None] 51 bytes
2018-11-01 16:45:28,797 - handlers.py[DEBUG]: finish: init-network/config-users-groups: SUCCESS: config-users-groups ran successfully
This issue is very bad one, as it can render your vm inaccessible on Azure.
I think this problem is due to the new kernel installation.
Initial bug report:
https://github.com/Azure/WALinuxAgent/issues/1386
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1803173/+subscriptions
References