[Bug 2013403] [NEW] lunar riscv64 preinstalled image shows login prompt before login is possible

Steve Langasek 2013403 at bugs.launchpad.net
Thu Mar 30 23:10:29 UTC 2023


Public bug reported:

Testing the lunar unmatched daily image in qemu, I was given a login
prompt on console and tried to log in, and it repeatedly failed.

This is because cloud-init had not finished running, so the user that
was provisioned via nocloud data was not actually available.

There should not be a race.  The login prompt should not be shown until
after the user exists - either by changing the ordering of the systemd
units, or by not using cloud-init to configure the initial user.  (I
don't see any obvious reason that a hard-coded initial user/password
should be done via cloud-init instead of being prepopulated in
/etc/passwd, but feel free to enlighten me.)

** Affects: cloud-init (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: livecd-rootfs (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to livecd-rootfs in Ubuntu.
https://bugs.launchpad.net/bugs/2013403

Title:
  lunar riscv64 preinstalled image shows login prompt before login is
  possible

Status in cloud-init package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New

Bug description:
  Testing the lunar unmatched daily image in qemu, I was given a login
  prompt on console and tried to log in, and it repeatedly failed.

  This is because cloud-init had not finished running, so the user that
  was provisioned via nocloud data was not actually available.

  There should not be a race.  The login prompt should not be shown
  until after the user exists - either by changing the ordering of the
  systemd units, or by not using cloud-init to configure the initial
  user.  (I don't see any obvious reason that a hard-coded initial
  user/password should be done via cloud-init instead of being
  prepopulated in /etc/passwd, but feel free to enlighten me.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/2013403/+subscriptions




More information about the foundations-bugs mailing list