yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #89623
[Bug 1986551] Re: Current kinetic ISO images not installable on s390x
I can confirm that this issue is fixed with the latest 'pending' ISO from today (Sept 1st):
https://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/kinetic-live-server-s390x.iso
Many thx!
I tried that on two systems and I was able to reach subiquity - so,
complete the initial basic network configuration.
I was able to complete the entire installation on one of the systems,
but faced another (independent) problem on the 2nd one - will open a
separate bug for that (LP#1988407).
But this bug can be closed now as Fix Released.
** Changed in: ubuntu-z-systems
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/1986551
Title:
Current kinetic ISO images not installable on s390x
Status in cloud-init:
Fix Released
Status in subiquity:
Invalid
Status in Ubuntu on IBM z Systems:
Fix Released
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.lxd.hook.conf -4b29-8a88-87b80c6b731
8.scope Ý0m.
Ý Ý0;32m OK Ý0m¨ Started Ý0;1;39msnap.subiquity.hoo -4a63-9355-e4654a5890c
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.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 ...)
To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1986551/+subscriptions