Auto-login to shell on serial does not always work in subiquity on s390x

[Frank Heimes]

The auto-login to a shell on serial console in subiquity on s390x does not work in all cases.

For example if subiquity fails (for whatever reason) and I'm selecting "Exit To Shell" on the error screen, like this:

====================================================================
  An error occurred during installation [ Help ]
====================================================================
  ┌──────────────────── An error has occurred ───────────────────┐
  │curtin command install │
  │ preparing for installation │
  │ configuring storage │
  │ running 'curtin block-meta simple' │
  │ curtin command block-meta │
  │ removing previous storage devices │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  └──────────────────────────────────────────────────────────────┘

                               [ View full log ]
                               [ Exit To Shell ]
                               [ Reboot Now ]

I usually just end up at a login prompt:

====================================================================
  An error occurred during installation [ Help ]
====================================================================
  ┌──────────────────── An error has occurred ───────────────────┐
  │curtin command install │
  │ preparing for installation │
  │ configuring storage │
  │ running 'curtin block-meta simple' │
  │ curtin command block-meta │
  │ removing previous storage devices │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  │ │
  └──────────────────────────────────────────────────────────────┘

                               [ View full log ]
                               [ Exit To Shell ]
Ubuntu Focal Fossa (development branch) ubuntu-server ttysclp0

ubuntu-server login:

But the login credentials specified earlier don't work here, yet.
One has to use user ubuntu-server and just hit <Enter> on password to login.
(If this is unknown to the user he is totally stuck and can't get back to subiquity UI and can only restart the installation.)

In a different situations, for example when the installation ran fine and the last screen is shown (where one can do the post-install Reboot), and one selects to "Exit to Shell", auto-login is working as expected:

================================================================================
  Installation complete! [ Help ]
================================================================================
  ┌──────────────────────────── Finished install! ───────────────────────────┐
  │ apply networking config ^│
  │ writing etc/fstab │
  │ configuring multipath │
  │ updating packages on target system │
  │ configuring pollinate user-agent on target │
  │ finalizing installation │
  │ running 'curtin hook' │
  │ curtin command hook │
  │ executing late commands │
  │final system configuration │
  │ configuring cloud-init │
  │ installing openssh │
  │ restoring apt configuration │
  │downloading and installing security updates ││
  │copying logs to installed system v│
  └──────────────────────────────────────────────────────────────────────────┘

                              [ View full log ]
                              [ Reboot ]

---

Installer shell session activated.

This shell session is running inside the installer environment. You
will be returned to the installer when this shell is exited, for
example by typing Control-D or 'exit'.

Be aware that this is an ephemeral environment. Changes to this
environment will not survive a reboot. If the install has started, the
installed system will be mounted at /target.
root@ubuntu-server:/#

(This bug is a spin off of an issue that was briefly mentioned in LP 1855127, but it's worth to separate it.)

[Frank Heimes (fheimes)]

This happens with subiquity 19.11.1, as used in the Focal daily ISO from Dec 2nd.

[Michael Hudson-Doyle (mwhudson)]

The exit to shell button on the end screen is gone now. I think this is fixed?

[Michael Hudson-Doyle (mwhudson)]

(maybe only on edge)

[Frank Heimes (fheimes)]

With subiquity from edge (19.12.2+git42.f925c3fa) I retried and entered the shell at different stages in the install process and auto-login always worked for me so far.
Hence I think this can be closed and status set to Fix Released.