[Bug 1933523] Re: Temporary installer password and key fingerprints are not printed with latest impish daily ISOs

[Michael Hudson-Doyle]

On Fri, 30 Jul 2021 at 21:11, Paride Legovini <1933523 at bugs.launchpad.net>
wrote:

> Hi, now as [1] landed if I don't go wrong we'll have to:
>
> - Wait for livecd-rootfs 2.664.25 to be accepted and installed
>   in the Focal archive.
> - Wait for new ISOs to be built and check from the cd-build-log [2]
>   which livecd build was used.
> - Check that livecd build log at [3] actually uses livecd-rootfs 2.664.25.
>   (The livecd-rootfs version is not included in the cd-build-log [2]).
> - If everything is as expected => Test the ISO.
>

More or less yes. But no ISO will be built using the livecd-rootfs from
proposed automatically, we'll have to ask someone to do that.

Cheers,
mwh

-- 
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/1933523

Title:
  Temporary installer password and key fingerprints are not printed with
  latest impish daily ISOs

Status in subiquity:
  Invalid
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in livecd-rootfs source package in Focal:
  In Progress

Bug description:
  [impact]
  cloud-init no longer puts the password of a user with a RANDOM password anywhere subiquity can find it, so while the password chosen ends up printed to the console, subiquity cannot display it from within the UI as it used to.

  [regression potential]
  If something goes wrong here, it's possible that subiquity will no longer be able to display the password for the installer user at all, which will make continuing the install via SSH impossible (this is very important for installing on z/vm)

  [test case]
  Make an ISO with this change and boot it and check that the installer password is available in the UI. Make a s390x ISO, boot it in z/vm and check that the installer password is displayed on the console.

  [original description]
  Using the latest Impish daily ISO (timestamp) 2021-06-24 I faced the situation that I didn't got a temporary installation password not the key fingerprints at the end of the installer boot-up process.

  Hence I am not able to perform an installation from remote via ssh.
  However, subiqity is started at the console (e.g. Integrated ASCII console) and an installation can be successfully completed there, but a console installation is not in all cases possible, for example with z/VM guests.

  As one can read between the lines I tried this on s390x (Integrated
  ASCII console and z/VM), but 'paride' tried the same on amd64 and ran
  into the same symptoms, so it does not seem to be architecture
  specific.

  This must have happened recently, since I already was able to do ssh-based Impish installations on s390x in the past (for example with the daily ISO from 06-14-2021).
  ___

  This is not the case for the 20.04 dailies - I can do remote ssh installation with the 20.04 live daily ISOs.
  ___

  With Impish on s390x the kernel parameter 'quiet' is still set by
  default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1933523/+subscriptions