In testing the just released F32 Beta in a QEMU/KVM, installed from Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too long. It pauses for 1min 30seconds for a stopped job. The journal shows.....
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: State 'stop-sigterm' timed out. Killing. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Killing process 1146 (spice-vdagentd) with signal SIGKILL. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Main process exited, code=killed, status=9/KILL Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Failed with result 'timeout'. Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped Agent daemon for Spice guests. Mar 15 16:46:25 f32k.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped target Basic System.
is this a known problem?
On 2020-03-15 16:53, Ed Greshko wrote:
In testing the just released F32 Beta in a QEMU/KVM, installed from Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too long. It pauses for 1min 30seconds for a stopped job. The journal shows.....
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: State 'stop-sigterm' timed out. Killing. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Killing process 1146 (spice-vdagentd) with signal SIGKILL. Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Main process exited, code=killed, status=9/KILL Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service: Failed with result 'timeout'. Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped Agent daemon for Spice guests. Mar 15 16:46:25 f32k.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped target Basic System.
is this a known problem?
I just noticed that spice-vdagent was upgraded after the install.
Downgrading from spice-vdagent-0.20.0-1.fc32 to spice-vdagent-0.19.0-5 resolves the issue.
I have created https://bugzilla.redhat.com/show_bug.cgi?id=1813667
On Sun, Mar 15, 2020 at 12:03 PM Ed Greshko ed.greshko@greshko.com wrote:
On 2020-03-15 16:53, Ed Greshko wrote:
In testing the just released F32 Beta in a QEMU/KVM, installed from
Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too long. It pauses for 1min 30seconds for a stopped job. The journal shows.....
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service:
State 'stop-sigterm' timed out. Killing.
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service:
Killing process 1146 (spice-vdagentd) with signal SIGKILL.
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service:
Main process exited, code=killed, status=9/KILL
Mar 15 16:46:25 f32k.greshko.com systemd[1]: spice-vdagentd.service:
Failed with result 'timeout'.
Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped Agent daemon for
Spice guests.
Mar 15 16:46:25 f32k.greshko.com audit[1]: SERVICE_STOP pid=1 uid=0
auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
Mar 15 16:46:25 f32k.greshko.com systemd[1]: Stopped target Basic
System.
is this a known problem?
I just noticed that spice-vdagent was upgraded after the install.
Downgrading from spice-vdagent-0.20.0-1.fc32 to spice-vdagent-0.19.0-5 resolves the issue.
I have created https://bugzilla.redhat.com/show_bug.cgi?id=1813667
Thanks Ed, for debugging this and reporting the issue. I can reproduce it, so I commented on the bug and also posted negative karma on that spice-vdagent update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d
If you can submit a negative karma as well, that's appreciated. Next time, if you spot such an issue, and the software is still in testing, please submit a negative karma asap, so that the broken update doesn't reach regular users. Thanks!
On 2020-03-17 00:30, Kamil Paral wrote:
On Sun, Mar 15, 2020 at 12:03 PM Ed Greshko <ed.greshko@greshko.com mailto:ed.greshko@greshko.com> wrote:
On 2020-03-15 16:53, Ed Greshko wrote: > In testing the just released F32 Beta in a QEMU/KVM, installed from Fedora-KDE-Live-x86_64-32_Beta-1.2.iso, I find that the shutdown takes too long. It pauses for 1min 30seconds for a stopped job. The journal shows..... > > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: spice-vdagentd.service: State 'stop-sigterm' timed out. Killing. > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: spice-vdagentd.service: Killing process 1146 (spice-vdagentd) with signal SIGKILL. > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: spice-vdagentd.service: Main process exited, code=killed, status=9/KILL > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: spice-vdagentd.service: Failed with result 'timeout'. > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: Stopped Agent daemon for Spice guests. > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=spice-vdagentd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed' > Mar 15 16:46:25 f32k.greshko.com <http://f32k.greshko.com> systemd[1]: Stopped target Basic System. > > is this a known problem? > > I just noticed that spice-vdagent was upgraded after the install. Downgrading from spice-vdagent-0.20.0-1.fc32 to spice-vdagent-0.19.0-5 resolves the issue. I have created https://bugzilla.redhat.com/show_bug.cgi?id=1813667
Thanks Ed, for debugging this and reporting the issue. I can reproduce it, so I commented on the bug and also posted negative karma on that spice-vdagent update: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d
If you can submit a negative karma as well, that's appreciated. Next time, if you spot such an issue, and the software is still in testing, please submit a negative karma asap, so that the broken update doesn't reach regular users. Thanks!
Ah, yes. Thanks for reminding me about that.
Unfortunately it seems I should not have slept. "Comments and Feedback are Closed"
On Tue, Mar 17, 2020 at 12:43 AM Ed Greshko ed.greshko@greshko.com wrote:
Thanks Ed, for debugging this and reporting the issue. I can reproduce
it, so I commented on the bug and also posted negative karma on that spice-vdagent update:
https://bodhi.fedoraproject.org/updates/FEDORA-2020-6ff500948d
If you can submit a negative karma as well, that's appreciated. Next
time, if you spot such an issue, and the software is still in testing, please submit a negative karma asap, so that the broken update doesn't reach regular users. Thanks!
Ah, yes. Thanks for reminding me about that.
Unfortunately it seems I should not have slept. "Comments and Feedback are Closed"
This is a pet peeve for QA, and it will no longer happen once Bodhi deploys a new version (we convinced them to revert that functionality). But it doesn't matter now, the update is stable :-/
On 2020-03-17 00:30, Kamil Paral wrote:
If you can submit a negative karma as well, that's appreciated. Next time, if you spot such an issue, and the software is still in testing, please submit a negative karma asap, so that the broken update doesn't reach regular users. Thanks!
Oh, I did just give negative karma to the F31 version.
On 2020-03-17 07:12, Ed Greshko wrote:
On 2020-03-17 00:30, Kamil Paral wrote:
If you can submit a negative karma as well, that's appreciated. Next time, if you spot such an issue, and the software is still in testing, please submit a negative karma asap, so that the broken update doesn't reach regular users. Thanks!
Oh, I did just give negative karma to the F31 version.
Oh, bugger...
I inadvertently tested on an F32 system which had been upgraded from F31 but still marked as F31. It didn't fail when tested in an actual F31VM. So, this version only exhibits a problem with F32.