This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1803173

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
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

-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to