[s390x] "Exit To Shell" does not bring to a shell

Bug #1823797 reported by Paride Legovini
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
subiquity
Invalid
Undecided
Unassigned

Bug Description

When subiquity encounters a problem the user is prompted to either view the full installation log, reboot, or exit to a shell (see attached screenshot). Selecting "Exit To Shell" brings to a login prompt instead of executing a shell. It is unclear if a valid username/password pair exists and allows to actually login.

This happens with both the latest daily ISO image (20190408) and with the disco beta image. The problem is reproducible by trying to install with virt-install (provided that the installer encounters a problem, of course!), e.g.:

virt-install --name test --ram 1024 --disk path=/path/to/test.qcow2,bus=virtio --cdrom ubuntu-19.04-beta-live-server-s390x.iso

Revision history for this message
Paride Legovini (paride) wrote :
Revision history for this message
Paride Legovini (paride) wrote :

I'm not sure if related, but while booting the following error message is printed:

  [FAILED] Failed to start Create System Users.

When given the "Exit To Shell" login prompt no reasonable default username/password pair works, so it *may* be that a default user hasn't been set up.

Revision history for this message
Paride Legovini (paride) wrote :

For the record, I've been hit by this bug while working at

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534162

and specifically at:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1534162/comments/5

which is the subiquity version of the original issue.

Revision history for this message
Paride Legovini (paride) wrote :

The problem affects serial terminals, and the reason is that serial getty it not configured for automatic login unlike regular getty.

It is possible to log in with username 'ubuntu-server' and no password.

Revision history for this message
Michael Hudson-Doyle (mwhudson) wrote :

I don't know if this is fixed or invalid or whatever but this whole feature is gone now so the bug is definitely closed!

Changed in subiquity:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.