Hello Dimitri,
After a quick check it looks like this service is still in inactive
(dead) state even after a reboot.
ubuntu@kernel04:/lib/systemd$ sudo systemctl status systemd-timesyncd
● systemd-timesyncd.service
Loaded: masked (Reason: Unit systemd-timesyncd.service is masked.)
Active: inactive (dead)
ubuntu@kernel04:/lib/systemd$ file /lib/systemd/system/systemd-timesyncd.service
/lib/systemd/system/systemd-timesyncd.service: cannot open
`/lib/systemd/system/systemd-timesyncd.service' (No such file or directory)
And there is no "systemd-timesyncd.service" file at where is should be.
So yeah it's not running, our testing tool did not check the state first
before trying to stop / start it.
$ sudo systemctl edit systemd-timesyncd
Cannot edit systemd-timesyncd.service: unit is masked.
Let me see if I can un-mask it.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1882505
Title:
ubuntu_ltp_syscalls failed to run on Focal s390x, unable to restart
systemd-timesyncd.service
Status in ubuntu-kernel-tests:
New
Status in systemd package in Ubuntu:
Incomplete
Bug description:
Issue found on 5.4.0-34.38 s390x LPAR / zVM
We need to stop timesyncd for the following tests:
['leapsec01','stime01','settimeofday01','clock_settime01']
But it looks like when we're trying to restart it:
systemctl start systemd-timesyncd
It will fail with:
Failed to start systemd-timesyncd.service: Unit systemd-timesyncd.service
is masked.
This issue did not happen on 5.4.0-33.37, the ubuntu_ltp_syscalls test can
finish with that kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882505/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
