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 notif
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 J
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 F
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 (Ubunt
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@Keschdeic
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
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 ru
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. Se
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
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 i
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
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/ubu
** 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/ubu
** 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
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 p
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)
I
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
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 thi
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 wo
** 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
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 --w
21 matches
Mail list logo
