Discussions revealed that it might also be interesting to check the
status of the virtlogd.socket before the update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738834
Title:
virtlogd should be r
Hmm, maybe another package of that upgrade pack restarts it which it
should not do.
I prepared an upgrade from Xenial to the Cloud Archive versions as initially
reported.
This comes down to the critical section being:
The following NEW packages will be installed:
libvirt-clients libvirt-daemon
This happens during the unattended-upgrade at night. The libvirt-bin is then
not fully upgraded/installed.
Jul 18 06:12:07 x systemd[1]: Reloading Virtual machine log manager.
Jul 18 06:12:07 x systemd[1]: Reloaded Virtual machine log manager.
Jul 18 06:12:09 x systemd[1]: Dependency failed for V
Here after an install of libvirt-daemon-system (which has the snippet to
reload)
systemctl status virtlogd --no-pager
...
Jun 26 10:37:11 x systemd[1]: Started Virtual machine log manager.
Jun 26 10:37:26 x systemd[1]: Reloading Virtual machine log manager.
Jun 26 10:37:26 x systemd[1]: Reloaded V
This was it:
The virtlogd daemon has the ability to re-exec() itself upon receiving SIGUSR1,
to allow live upgrades without downtime.
** Changed in: libvirt (Ubuntu)
Importance: Low => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
>From http://manpages.ubuntu.com/manpages/bionic/man8/virtlogd.8.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738834
Title:
virtlogd should be restarted on upgrade
To manage notifications ab
For that it has:
ExecReload=/bin/kill -USR1 $MAINPID
defined and would do the right thing.
** Bug watch added: Debian Bug tracker #833745
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833745
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
But that should be done in postinst:
129 # Force virtlockd to reexec if enabled
130 if [ -d /run/systemd/system ]; then
131 ! systemctl is-active -q virtlogd || systemctl reload
virtlogd.service >/
Another way to hit this upgrade path is Xenial using libvirt and then
upgrading to Cloud-Archive Pike (Artful based).
Since we already have 18.04/Queens which also is longer supported I
tried with that.
This most likely is due to "--no-restart-on-upgrade" that is used for virtlogd.
Which was actu
It looks like there is no other scenario for this upgrade to happen
naturally between the versions 1.3.1 and 3.6.0 other than a release
upgrade in ubuntu, right? And that would require a reboot at the end.
Given that, I'll mark this as "low" priority for now until further data
about why reload/ree
Could it be related to
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1583009
-J
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1738834
Title:
virtlogd should be restarted on upgrade
To man
Looking at postinst, I see virtlogd is reloaded. I have checked that
reload trigger a reexec (like expected). Therefore, I don't know why
this is not enough. I should investigate more on this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
12 matches
Mail list logo
