[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
This bug was fixed in the package uvtool - 0~git169-0ubuntu1.20.04.2 --- uvtool (0~git169-0ubuntu1.20.04.2) focal; urgency=medium * d/p/lp-2095042-*: fix wait for plucky onwards (LP: #2095042) -- Christian Ehrhardt Wed, 22 Jan 2025 07:47:37 +0200 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
This bug was fixed in the package uvtool - 0~git183-0ubuntu1.24.04.1 --- uvtool (0~git183-0ubuntu1.24.04.1) noble; urgency=medium * d/p/lp-2095042-*: fix wait for plucky onwards (LP: #2095042) -- Christian Ehrhardt Mon, 20 Jan 2025 08:27:08 +0200 ** Changed in: uvtool (Ubuntu Jammy) 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
This bug was fixed in the package uvtool - 0~git178-0ubuntu1.22.04.2 --- uvtool (0~git178-0ubuntu1.22.04.2) jammy; urgency=medium * d/p/lp-2095042-*: fix wait for plucky onwards (LP: #2095042) -- Christian Ehrhardt Wed, 22 Jan 2025 07:47:37 +0200 ** Changed in: uvtool (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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
This bug was fixed in the package uvtool - 0~git183-0ubuntu1.24.10.1 --- uvtool (0~git183-0ubuntu1.24.10.1) oracular; urgency=medium * d/p/lp-2095042-*: fix wait for plucky onwards (LP: #2095042) -- Christian Ehrhardt Mon, 20 Jan 2025 08:27:08 +0200 ** Changed in: uvtool (Ubuntu Oracular) Status: Fix Committed => Fix Released ** Changed in: uvtool (Ubuntu Noble) 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
And now test the old vs the fixed wait script - example here is from noble but it looks the same in all host releases. As mentioned the noble vs plucky here is not host but guest release that we compare as that is where the behavior changed. 1. check if guests are up and respond paelzer@Keschdeichel 12:10:08 1 ~ uvt-kvm ssh n uptime 11:10:23 up 0 min, 1 user, load average: 0.92, 0.22, 0.07 paelzer@Keschdeichel 12:10:25 ~ uvt-kvm ssh p uptime 11:10:28 up 0 min, 2 users, load average: 0.85, 0.26, 0.09 2. check for the reported issue directly paelzer@Keschdeichel 12:11:00 130 ~ uvt-kvm ssh n runlevel N 5 paelzer@Keschdeichel 12:11:07 ~ uvt-kvm ssh p runlevel unknown => we see that it never gets into a proper state 3. check how that translated into the hang in the wait script before the fix paelzer@Keschdeichel 12:11:10 1 ~ md5sum /usr/share/uvtool/libvirt/remote-wait.sh 3bf4076b196e49e6cae83968d5b67cca /usr/share/uvtool/libvirt/remote-wait.sh paelzer@Keschdeichel 12:11:50 ~ time uvt-kvm wait n real0m1,023s user0m0,571s sys 0m0,120s works for e.g. noble Fails for plucky (I aborted it) paelzer@Keschdeichel 12:11:54 ~ time uvt-kvm wait p ^CTraceback (most recent call last): File "/usr/bin/uvt-kvm", line 35, in uvtool.libvirt.kvm.main_cli_wrapper(sys.argv[1:]) File "/usr/lib/python3/dist-packages/uvtool/libvirt/kvm.py", line 1118, in main_cli_wrapper main(*args, **kwargs) File "/usr/lib/python3/dist-packages/uvtool/libvirt/kvm.py", line 1113, in main args.func(parser, args) File "/usr/lib/python3/dist-packages/uvtool/libvirt/kvm.py", line 1028, in main_wait main_wait_remote(parser, args) File "/usr/lib/python3/dist-packages/uvtool/libvirt/kvm.py", line 972, in main_wait_remote ssh( File "/usr/lib/python3/dist-packages/uvtool/libvirt/kvm.py", line 836, in ssh result = call( ^ File "/usr/lib/python3.12/subprocess.py", line 408, in check_call retcode = call(*popenargs, **kwargs) ^^ File "/usr/lib/python3.12/subprocess.py", line 391, in call return p.wait(timeout=timeout) ^^^ File "/usr/lib/python3.12/subprocess.py", line 1264, in wait return self._wait(timeout=timeout) ^^^ File "/usr/lib/python3.12/subprocess.py", line 2053, in _wait (pid, sts) = self._try_wait(0) ^ File "/usr/lib/python3.12/subprocess.py", line 2011, in _try_wait (pid, sts) = os.waitpid(self.pid, wait_flags) KeyboardInterrupt real0m17,535s user0m0,537s sys 0m0,113s 4. upgrade this machine as well to the new wait script paelzer@Keschdeichel 12:12:40 ~ sudo apt install uvtool-libvirt -t noble-proposed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: uvtool-libvirt 1 upgraded, 0 newly installed, 0 to remove and 175 not upgraded. Need to get 29,6 kB of archives. After this operation, 1.024 B of additional disk space will be used. Get:1 http://de.archive.ubuntu.com/ubuntu noble-proposed/universe amd64 uvtool-libvirt all 0~git183-0ubuntu1.24.04.1 [29,6 kB] Fetched 29,6 kB in 0s (162 kB/s) (Reading database ... 352705 files and directories currently installed.) Preparing to unpack .../uvtool-libvirt_0~git183-0ubuntu1.24.04.1_all.deb ... Unpacking uvtool-libvirt (0~git183-0ubuntu1.24.04.1) over (0~git183-0ubuntu1) ... Setting up uvtool-libvirt (0~git183-0ubuntu1.24.04.1) ... Processing triggers for man-db (2.12.0-4build2) ... paelzer@Keschdeichel 12:13:00 ~ md5sum /usr/share/uvtool/libvirt/remote-wait.sh a373cc413dd803557a077b38f0cf5b09 /usr/share/uvtool/libvirt/remote-wait.sh 5. verify the new script works on old and new guests Still working on noble guest paelzer@Keschdeichel 12:13:19 ~ time uvt-kvm wait n real0m0,913s user0m0,537s sys 0m0,117s paelzer@Keschdeichel 12:13:54 ~ time uvt-kvm wait p running real0m0,807s user0m0,513s sys 0m0,090s Works - setting verified for all releases that share the wait code. ** Tags removed: verification-needed verification-needed-focal verification-needed-jammy verification-needed-noble verification-needed-oracular ** Tags added: verification-done verification-done-focal verification-done-jammy verification-done-noble verification-done-oracular -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
First ensure upgrades are going through fine in all releases root@f-sru:~# apt install uvtool-libvirt Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be upgraded: uvtool-libvirt 1 upgraded, 0 newly installed, 0 to remove and 24 not upgraded. Need to get 30.9 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 uvtool-libvirt all 0~git169-0ubuntu1.20.04.2 [30.9 kB] Fetched 30.9 kB in 0s (95.3 kB/s) (Reading database ... 48691 files and directories currently installed.) Preparing to unpack .../uvtool-libvirt_0~git169-0ubuntu1.20.04.2_all.deb ... Unpacking uvtool-libvirt (0~git169-0ubuntu1.20.04.2) over (0~git169-0ubuntu1.20.04.1) ... Setting up uvtool-libvirt (0~git169-0ubuntu1.20.04.2) ... Processing triggers for man-db (2.9.1-1) ... root@j-sru:~# apt install uvtool-libvirt Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: uvtool-libvirt 1 upgraded, 0 newly installed, 0 to remove and 46 not upgraded. Need to get 31.0 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 uvtool-libvirt all 0~git178-0ubuntu1.22.04.2 [31.0 kB] Fetched 31.0 kB in 0s (295 kB/s) (Reading database ... 74470 files and directories currently installed.) Preparing to unpack .../uvtool-libvirt_0~git178-0ubuntu1.22.04.2_all.deb ... Unpacking uvtool-libvirt (0~git178-0ubuntu1.22.04.2) over (0~git178-0ubuntu1.22.04.1) ... Setting up uvtool-libvirt (0~git178-0ubuntu1.22.04.2) ... Processing triggers for man-db (2.10.2-1) ... Scanning processes... Scanning linux images... root@n-sru:~# apt install uvtool-libvirt -t noble-proposed Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: uvtool-libvirt 1 upgraded, 0 newly installed, 0 to remove and 124 not upgraded. Need to get 29.6 kB of archives. After this operation, 1024 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu noble-proposed/universe amd64 uvtool-libvirt all 0~git183-0ubuntu1.24.04.1 [29.6 kB] Fetched 29.6 kB in 0s (114 kB/s) (Reading database ... 90868 files and directories currently installed.) Preparing to unpack .../uvtool-libvirt_0~git183-0ubuntu1.24.04.1_all.deb ... Unpacking uvtool-libvirt (0~git183-0ubuntu1.24.04.1) over (0~git183-0ubuntu1) ... Setting up uvtool-libvirt (0~git183-0ubuntu1.24.04.1) ... Processing triggers for man-db (2.12.0-4build2) ... Scanning processes... Scanning linux images... root@o-sru:~# apt install uvtool-libvirt -t oracular-proposed Upgrading: uvtool-libvirt Summary: Upgrading: 1, Installing: 0, Removing: 0, Not Upgrading: 38 Download size: 29.6 kB Space needed: 1024 B / 6667 MB available Get:1 http://archive.ubuntu.com/ubuntu oracular-proposed/universe amd64 uvtool-libvirt all 0~git183-0ubuntu1.24.10.1 [29.6 kB] Fetched 29.6 kB in 0s (91.2 kB/s) (Reading database ... 92960 files and directories currently installed.) Preparing to unpack .../uvtool-libvirt_0~git183-0ubuntu1.24.10.1_all.deb ... Unpacking uvtool-libvirt (0~git183-0ubuntu1.24.10.1) over (0~git183-0ubuntu1) ... Setting up uvtool-libvirt (0~git183-0ubuntu1.24.10.1) ... Processing triggers for man-db (2.12.1-3) ... Scanning processes... Scanning linux images... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
I first set up plucky (should show the problem we fix) and noble (reference to not get broken by the change) guests that were up and running just fine on hosts being of F/J/N/O release. The interesting bit here is that we test "against" guest releases and the host would not matter that much. It runs the wait script, by default /usr/share/uvtool/libvirt/remote-wait.sh against the guest and it needs to return when it is ready. Functionally they are all the same in all releases, prior to the update: root@f-sru:~# md5sum /usr/share/uvtool/libvirt/remote-wait.sh 3bf4076b196e49e6cae83968d5b67cca /usr/share/uvtool/libvirt/remote-wait.sh (same in J/N/O) After upgrade on all releases root@j-sru:~# md5sum /usr/share/uvtool/libvirt/remote-wait.sh a373cc413dd803557a077b38f0cf5b09 /usr/share/uvtool/libvirt/remote-wait.sh -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Hello Sergio, or anyone else affected, Accepted uvtool into oracular-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/uvtool/0~git183-0ubuntu1.24.10.1 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- oracular to verification-done-oracular. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-oracular. 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: uvtool (Ubuntu Oracular) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-oracular ** Changed in: uvtool (Ubuntu Noble) Status: In Progress => Fix Committed ** Tags added: verification-needed-noble -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
MR review complete, uploaded to -unapproved ** Tags added: server-todo ** Changed in: uvtool (Ubuntu Focal) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: uvtool (Ubuntu Noble) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: uvtool (Ubuntu Jammy) Assignee: (unassigned) => Christian Ehrhardt (paelzer) ** Changed in: uvtool (Ubuntu Focal) Status: New => In Progress ** Changed in: uvtool (Ubuntu Jammy) Status: New => In Progress ** Changed in: uvtool (Ubuntu Noble) Status: New => In Progress ** Changed in: uvtool (Ubuntu Oracular) Status: New => In Progress ** Changed in: uvtool (Ubuntu Oracular) Assignee: (unassigned) => Christian Ehrhardt (paelzer) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Thanks for the feedback. Gladly if VERSION_ID is empty the code goes to the old behavior, which means there is no change to non-Ubuntu handling (which matches the spirit of SRUs to avoid changing/regressing something else). I'd indeed not want to re-roll all of it - but happy if there is a real issue reported around it. In that case more conditions can opt into the the new path being `systemctl is-system-running --wait`. Forward it might be reasonable to make it the default, but now and for the SRU I'd want to avoid that. ** Description changed: + [ Impact ] + + * New releases no more can check for runlevel (see details +in the original report) + + * Treat plucky onward like that and use +`systemctl is-system-running --wait` there + + [ Test Plan ] + + * Compare the behavior of uvtool creating and starting guests on the +target releases we apply this SRU to. In particular use guests of +e.g. Noble (old behavior) and Plucky (new behavior). +Ensure to use the --wait option which is what we are changing here + + [ Where problems could occur ] + + * Changes are isolated to --wait, the code tries to tolerate e.g. a +missing VERSION_ID (fallback to old behavior). Due to that the wait +behavior is what to watch out for if e.g. this detection goes mad. + + [ Other Info ] + + * The upload is the same change for all releases which should make +it easier to review. + + --- original report --- + Hi, Plucky uses login(1) from util-linux instead of shadow, which means that utmp will not be updated anymore. This is what systemd's runlevel shim uses to determine the current runlevel, so from Plucky onwards running "runlevel" will return "unknown". "uvt-kvm wait"'s remote-wait-script relies on runlevel to determine whether the virtual machine is ready, and when executed against a Plucky VM the script will enter an infinite loop waiting for "runlevel" to return a valid output. The script needs to be updated to take into account systemd systems. I am locally relying on "systemctl get-default", but I'm not sure if it's enough. Debian's autopkgtest project also had to deal with this problem, and this is what they did: https://salsa.debian.org/ci-team/autopkgtest/-/commit/677af48 Maybe "systemctl is-system-running" is more trustworthy. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
A couple of thoughts, though maybe too late to be worth amending now: 1) I'd treat `systemctl is-system-running --wait` as the default, and make all older methods as conditional exceptions for releases that require it. 2) Checking VERSION_ID is invalid unless ID is validated to be "ubuntu". I don't know how much uvtool is used for other distros, but theoretically it can be so it'd be nice to keep remote-wait.sh as generic as possible. Hence my previous point. But this is probably insignificant enough not to be worth changing now. I'm fine with an SRU straight backport and only worrying about that case if it comes up, since it seems so unlikely. As an example, I downloaded a Debian cloud image and used uvtool with --backing-image-file to boot it not that long ago. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
PPA: https://launchpad.net/~paelzer/+archive/ubuntu/lp-2095042-new-wait MRs: - F https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479887 - J https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479888 - N https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479890 - O https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479891 Hi Sergio, here are MRs and builds prepared for all active releases - I hope this is easy to review. The SRU test and impact sections seem trivial to write but I have to run to the sessions here. I wanted to ask if you still have output of the bad (might not say much hanging) and good state already that you could copy and paste. If not fine, I'll add that then when I get to add the template. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479887 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479888 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479890 ** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/uvtool/+git/uvtool/+merge/479891 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
** Also affects: uvtool (Ubuntu Oracular) 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
This bug was fixed in the package uvtool - 0~git186-0ubuntu1 --- uvtool (0~git186-0ubuntu1) plucky; urgency=medium * wait: 25.04 can't reliably use runlevel anymore. Keep handling of former releases unchanged, but use systemd is-system-running --wait for guests being 25.04 plucky or newer (LP: #2095042) -- Christian Ehrhardt Mon, 20 Jan 2025 07:57:11 +0200 ** Changed in: uvtool (Ubuntu) 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Went through the steps of creating a new tarball and uploaded a new version to plucky. ** Also affects: uvtool (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: uvtool (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: uvtool (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: uvtool (Ubuntu) Status: New => 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/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Fix merged in the project itself now ... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Thanks, Christian. Reviewed and approved. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
Sergio, what do you think of https://code.launchpad.net/~paelzer/uvtool/+git/uvtool/+merge/479550 ? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
** Merge proposal linked: https://code.launchpad.net/~paelzer/uvtool/+git/uvtool/+merge/479550 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 2095042] Re: uvt-kvm remote-wait-script doesn't work from Plucky onwards
The final "ready" is the check for /var/lib/cloud/instance/boot-finished anyway. So indeed this now entering an infinite loop just blocks it from ever learning about it. "systemctl is-system-running" is more trustworthy indeed and even has he feature we'd wait without polling. From [1]: "Use --wait to wait until the boot process is completed before printing the current state and returning the appropriate error status. If --wait is in use, states initializing or starting will not be reported, instead the command will block until a later state (such as running or degraded) is reached." We do not even need to check the state, it will wait in the phases that are too early, and then look for the cloud init stamp in the second step. That --wait is available since the systemd in Focal, but we should go by >=Plucky to avoid changing behavior anyway. [1]: https://www.freedesktop.org/software/systemd/man/latest/systemctl.html#is- system-running -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2095042 Title: uvt-kvm remote-wait-script doesn't work from Plucky onwards To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/uvtool/+bug/2095042/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
