Current kinetic ISO images not installable on s390x
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Fix Released
|
High
|
Canonical Foundations Team | ||
cloud-init |
Fix Released
|
High
|
James Falcon | ||
subiquity |
Invalid
|
Undecided
|
Unassigned |
Bug Description
While wanting to install an kinetic/22.10 system on s390x for testing new and updated packages
I found that the current daily ISO image for s390x is not installable - not on LPAR nor on z/VM - not interactively using subiquity, not non-interactively using autoinstall.
I had the image from August 2nd and the installation ended at the console with these messages (please ignore the weird special characters):
...
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mTime & Date Service Ý0m.
connecting... - \ |
waiting for cloud-init... -
It is possible to connect to the installer over the network, which
might allow the use of a more capable terminal and can offer more languages
than can be rendered in the Linux console.
Unfortunately this system seems to have no global IP addresses at this
time.
Starting Ý0;1;39mTime & Date Service Ý0m...
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mTime & Date Service Ý0m.
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mWait until snapd is fully seeded Ý0m.
Starting Ý0;1;39mApply the settings specified in cloud-config Ý0m...
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mSubiquity, the installer for Ubuntu Server
hvc0 Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mSubiquity, the ins er for Ubuntu Server t
tysclp0 Ý0m.
Ý Ý0;32m OK Ý0m¨ Reached target Ý0;1;39mLogin Prompts Ý0m.
Stopping Ý0;1;39mOpenBSD Secure Shell server Ý0m...
Ý Ý0;32m OK Ý0m¨ Stopped Ý0;1;39mOpenBSD Secure Shell server Ý0m.
Starting Ý0;1;39mOpenBSD Secure Shell server Ý0m...
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mOpenBSD Secure Shell server Ý0m.
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mApply the settings specified in cloud-con
ig Ý0m.
Ý Ý0;32m OK Ý0m¨ Reached target Ý0;1;39mMulti-User System Ý0m.
Ý Ý0;32m OK Ý0m¨ Reached target Ý0;1;39mGraphical Interface Ý0m.
Starting Ý0;1;39mExecute cloud user/final scripts Ý0m...
Starting Ý0;1;39mRecord Runlevel Change in UTMP Ý0m...
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mRecord Runlevel Change in UTMP Ý0m.
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mExecute cloud user/final scripts Ý0m.
Ý Ý0;32m OK Ý0m¨ Reached target Ý0;1;39mCloud-init target Ý0m.
...
Then updated to the latest ISO from today (Aug 15th), I got the same:
...
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mHolds Snappy daemon refresh Ý0m.
Ý Ý0;32m OK Ý0m¨ Finished Ý0;1;39mService for snap application lxd.activate
Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39msnap.
8.scope Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39msnap.
1.scope Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mService for snap a on subiquity.subiquity
-server Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mService for snap a n subiquity.
service Ý0m.
Starting Ý0;1;39mTime & Date Service Ý0m...
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39mTime & Date Service Ý0m.
connecting... - \ |
waiting for cloud-init... - \
It is possible to connect to the installer over the network, which
might allow the use of a more capable terminal and can offer more languages
than can be rendered in the Linux console.
Unfortunately this system seems to have no global IP addresses at this
time.
...
Unfortunately I am not able to get any logs at that (very early) stage of the installation.
On top I did a 22.04.1 installation on the same systems, using the same data (IP etc) which worked fine.
(I kept one of the systems in that stage for now ...)
Changed in ubuntu-z-systems: | |
importance: | Undecided → High |
assignee: | nobody → Canonical Foundations Team (canonical-foundations) |
tags: |
added: installer rls-kk-incoming removed: subiquity |
After having a bit brainstormed with Michael on this, I have some updates:
If the installer is at the above stage (using the interactive way to specify the basic network config data <casper>, no login credentials are specified (like shown above),
but an ssh server is up and listening:
z/VM: t/LLOGMeNBD623B ac371TmcHBHD+ lthnY. [fingerprint] )? yes 10.123. 234.23' (ECDSA) to the list of known hosts.
$ ssh installer@hwe0003
The authenticity of host 'hwe0003 (10.123.234.23)' can't be established.
ECDSA key fingerprint is SHA256:
Are you sure you want to continue connecting (yes/no/
Warning: Permanently added 'hwe0003,
installer@hwe0003's password:
LPAR: 10.245. 236.14 41LjqXjab4D9rve xGhFo7+ OvBx5o. [fingerprint] )? yes 10.123. 234.14' s password: 10.123. 234.14' s password:
$ ssh ubuntu@
The authenticity of host '10.123.234.14 (10.123.234.14)' can't be established.
ECDSA key fingerprint is SHA256:
Are you sure you want to continue connecting (yes/no/
Warning: Permanently added '10.123.234.14' (ECDSA) to the list of known hosts.
ubuntu@
Permission denied, please try again.
ubuntu@
There are just no credentials to login.
But on LPAR, there is the additional option to do an installation based on the "Integrated ASCII console" (instead of using a remote ssh session).
And the subiquity installer shows up at "Integrated ASCII console", and allows to enter the installer shell.
'ip a' shows a proper IP address.
So the "Integrated ASCII console" can be used for further debugging ...