[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: ubuntu-z-systems Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
This bug was fixed in the package livecd-rootfs - 2.664.27 --- livecd-rootfs (2.664.27) focal; urgency=medium * And whoops, we missed adding ARCH in the SUBARCH ubuntu-image handling for intel-iot. livecd-rootfs (2.664.26) focal; urgency=medium * Revert previous change of fixing /dev sharing - this causes weird autopkgtest issues. livecd-rootfs (2.664.25) focal; urgency=medium [ Brian Murray ] * Add support for creating images (ubuntu-core and classic) with a kernel optimized for Intel IoT devices. (LP: #1938338) [ Michael Hudson-Doyle ] * Simplify how the subiquity client is run on the serial console in the live server environment, breaking a unit cycle that sometimes prevents subiquity from starting up at all. (LP: #1888497) * Do not set the password for the installer user via cloud-init as subiquity can now do this itself. (LP: #1933523) [ Łukasz 'sil2100' Zemczak ] * Fix sharing of the /dev tree to make sure we can safely umount the chroot when needed. This fixes local non-livefs-builder image builds. (LP: #1938414) -- Łukasz 'sil2100' Zemczak Wed, 04 Aug 2021 17:32:37 +0200 ** Changed in: livecd-rootfs (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
I tested the updated livecd-rootfs that is part of the new live-server image that Łukasz created: http://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/20210805.1/ and did a couple of installations (mainly LPAR, but DASD and FCP) and so far the boot-up of the installer always succeeded, and the remote ssh login was always possible. So I consider this now as successfully verified and think that we can close this ticket. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
As requested, I ran a server-live build with proposed enabled: http://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/20210805.1/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
Hello Frank, or anyone else affected, Accepted livecd-rootfs into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/livecd- rootfs/2.664.26 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: livecd-rootfs (Ubuntu Focal) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: livecd-rootfs (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Merge proposal linked: https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/406127 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Description changed: - From time to time (sporadically and very rarely - maybe in one or two - attempt out of twenty) I face a situation where the installer system (on - s390x) does not boot-up completely. + [impact] + When there is a serial console configured, there was a unit cycle + + serial-getty@$TTY.service -> cloud-final.service -> multi-user.target -> + getty.target -> serial-getty@$TTY.service + + (or something like that) + + Depending on which unit systemd kills to resolve the cycle, this can + result in cloud-init never completing which leads to the subiquity + server waiting forever for it and nothing useful can be done (other than + restarting and hoping for better luck next time). + + Because subiquity itself waits for cloud-init (and this has been true + for a long time now) there is no need for serial-getty@$TTY.service to + wait on cloud-final.service. + + [regression potential] + This change results in shuffling the systemd units around a fair bit, but the new arrangement has been tested in devel for a few months now and works well there. It's also much more straightforward than the current setup. + + [test case] + This is a bit tricky as it's an intermittent failure. Basically, boot the live installer with a serial console configured a bunch of times and (10?) check that the installer starts up properly each time. + + [original description] + From time to time (sporadically and very rarely - maybe in one or two attempt out of twenty) I face a situation where the installer system (on s390x) does not boot-up completely. This happened to me in the past already, but since it happened only one or twice I thought it's due to resource constraints on the system or so. But since I faced it now again on LPAR (before it was on z/VM), I'm opening this ticket now. In the latest case I used the focal daily live image from the 20th of July with installer 20.06.1 (but that also happened with previous versions). The situation is like this: In boot of the installer ends here (LPAR): ... "[ 128.200711] cloud-init[1375]: The key's randomart image is:" "[ 128.200735] cloud-init[1375]: +--[ED25519 256]--+" "[ 128.200758] cloud-init[1375]: |o .ooo |" "[ 128.200781] cloud-init[1375]: |.= . . +. o. .|" "[ 128.200804] cloud-init[1375]: |+ * . . * o.o . |" "[ 128.200826] cloud-init[1375]: |.= o . = = = + |" "[ 128.200849] cloud-init[1375]: |o + . S o +|" "[ 128.200876] cloud-init[1375]: | + o = . . |" "[ 128.200900] cloud-init[1375]: |o + .|" "[ 128.200925] cloud-init[1375]: | o.=. E |" "[ 128.200947] cloud-init[1375]: | .+.o+o. |" "[ 128.200977] cloud-init[1375]: +[SHA256]-+" "[ 138.898906] cloud-init[2217]: Cloud-init v. 20.2-45-g5f7825e2-0ubuntu1~20.04." "1 running 'modules:config' at Wed, 22 Jul 2020 11:27:39 +. Up 138.77 seconds" . "[ 138.898966] cloud-init[2217]: Set the following 'random' passwords" "[ 138.899001] cloud-init[2217]: installer:aecmewaoicnai" or another example (z/VM): ... - ¬ 93.463680| cloud-init¬1282|: +--¬ED25519 256|--+ - ¬ 93.463713| cloud-init¬1282|: !Eo=o ! - ¬ 93.463749| cloud-init¬1282|: !.Bo.o ... o ! - ¬ 93.463782| cloud-init¬1282|: !**.*... o = ! - ¬ 93.463818| cloud-init¬1282|: !*=O o. o . . ! - ¬ 93.463849| cloud-init¬1282|: !**++S! - ¬ 93.463886| cloud-init¬1282|: !§o+..! - ¬ 93.463918| cloud-init¬1282|: !+*o. ! - ¬ 93.463954| cloud-init¬1282|: !.o. ! - ¬ 93.463988| cloud-init¬1282|: !.! - ¬ 93.464028| cloud-init¬1282|: +¬SHA256|-+ + ¬ 93.463680| cloud-init¬1282|: +--¬ED25519 256|--+ + ¬ 93.463713| cloud-init¬1282|: !Eo=o ! + ¬ 93.463749| cloud-init¬1282|: !.Bo.o ... o ! + ¬ 93.463782| cloud-init¬1282|: !**.*... o = ! + ¬ 93.463818| cloud-init¬1282|: !*=O o. o . . ! + ¬ 93.463849| cloud-init¬1282|: !**++S! + ¬ 93.463886| cloud-init¬1282|: !§o+..! + ¬ 93.463918| cloud-init¬1282|: !+*o. ! + ¬ 93.463954| cloud-init¬1282|: !.o. ! + ¬ 93.463988| cloud-init¬1282|: !.! + ¬ 93.464028| cloud-init¬1282|: +¬SHA256|-+ ¬ 104.841438| cloud-init¬2004|: Cloud-init v. 20.2-45-g5f7825e2-0ubuntu1ß20.04. 1 running 'modules:config' at Mon, 20 Jul 2020 10:46:38 +. Up 104.63 seconds - . - ¬ 104.841490| cloud-init¬2004|: Set the following 'random' passwords - ¬ 104.841516| cloud-init¬2004|: installer:U9NJDuvXFw6X2fxG7pP8 + . + ¬ 104.841490| cloud-init¬2004|: Set the following 'random' passwords + ¬ 104.841516| cloud-init¬2004|: installer:U9NJDuvXFw6X2fxG7pP8 But it is not complete at this point. A completed boot of the installer system ends like this: "It is possible to connect to the installer over the network, which" "might allow the use of a more
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Merge proposal linked: https://code.launchpad.net/~mwhudson/livecd-rootfs/+git/livecd-rootfs/+merge/406126 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1888497] Re: Booting the install system does not always succeed, hence a remote ssh login is not always possible
** Changed in: subiquity Status: In Progress => Invalid ** Also affects: livecd-rootfs (Ubuntu) Importance: Undecided Status: New ** Changed in: livecd-rootfs (Ubuntu) Status: New => Fix Released ** Also affects: livecd-rootfs (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1888497 Title: Booting the install system does not always succeed, hence a remote ssh login is not always possible To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1888497/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
