Nope. I get essentially the same thing
Jun 18 16:40:00 <host> systemd[1]: Starting sysstat-collect.service - system
activity accounting tool...
Jun 18 16:40:00 <host> systemd[1]: sysstat-collect.service: Deactivated
successfully.
Jun 18 16:40:00 <host> systemd[1]: Finished sysstat-collect.service - system
activity accounting tool.
Jun 18 16:40:00 <host> audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295
ses=4294967295 subj=unconfined msg='unit=sysstat-collect comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 18 16:40:00 <host> audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295
ses=4294967295 subj=unconfined msg='unit=sysstat-collect comm="systemd"
exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jun 18 16:40:00 <host> kernel: audit: type=1130 audit(1781800800.903:416):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined
msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 18 16:40:00 <host> kernel: audit: type=1131 audit(1781800800.903:417):
pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined
msg='unit=sysstat-collect comm="systemd" exe="/usr/lib/systemd/systemd"
hostname=? addr=? terminal=? res=success'
Jun 18 16:40:13 <host> systemd[1]: Reload requested from client PID <pid>
('systemctl') (unit session-1.scope)...
Jun 18 16:40:13 <host> systemd[1]: Reloading...
Jun 18 16:40:14 <host> systemd[1]:
/usr/lib/systemd/system/xfs_scrub_all.service:26: Support for option
CPUAccounting= has been removed and it is ignored
Jun 18 16:40:14 <host> systemd[1]:
/usr/lib/systemd/system/system-xfs_scrub.slice:15: Support for option
CPUAccounting= has been removed and it is ignored
Jun 18 16:40:14 <host> systemd[1]: /usr/lib/systemd/system/frr.service:20:
PIDFile= references a path below legacy directory /var/run/, updating
/var/run/frr/watchfrr.pid → /run/frr/watchfrr.pid; please update the unit file
accordingly.
Jun 18 16:40:14 <host> systemd[1]: Reloading finished in 302 ms.
Nothing interesting either when I manually generate netplan-ovs-
cleanup.service then run `netplan apply`.
Which I point out because I don't know if it actually _is_ being
created, but something else in the pipeline is destroying it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2156406
Title:
`netplan apply` fails on systems without OVS
To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2156406/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
