timedatectl reports wrong status for timesyncd in core18

Bug #1885901 reported by Oliver Grawert on 2020-07-01
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Status tracked in Groovy
Bionic
Undecided
Unassigned
Focal
Undecided
Unassigned
Groovy
Undecided
Unassigned

Bug Description

when calling timedatectl in Ubuntu Core 18 the tool reports the status of the
systemd-timesyncd.service ...

sadly it does report it wrongly (the tool reports it inactive while the service is actually running):

ogra@pi4:~$ timedatectl
                      Local time: Wed 2020-07-01 10:52:48 UTC
                  Universal time: Wed 2020-07-01 10:52:48 UTC
                        RTC time: n/a
                       Time zone: n/a (UTC, +0000)
       System clock synchronized: yes
systemd-timesyncd.service active: no
                 RTC in local TZ: no
ogra@pi4:~$ systemctl status systemd-timesyncd.service
● systemd-timesyncd.service - Network Time Synchronization
   Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; disabled; vendor preset: enabled)
   Active: active (running) since Tue 2020-06-30 18:06:18 UTC; 16h ago
     Docs: man:systemd-timesyncd.service(8)
 Main PID: 779 (systemd-timesyn)
   Status: "Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com)."
    Tasks: 2 (limit: 4915)
   CGroup: /system.slice/systemd-timesyncd.service
           └─779 /lib/systemd/systemd-timesyncd

Oliver Grawert (ogra) wrote :

any fix should be SRUed into the respective LTS releases for Ubuntu Core, added tasks for them

Balint Reczey (rbalint) wrote :

Works in Ubuntu Classic it seems.
Where are Ubuntu Core bugs tracked? Please reassign this but there.

Changed in systemd (Ubuntu Groovy):
status: New → Invalid
Changed in systemd (Ubuntu Focal):
status: New → Invalid
Changed in systemd (Ubuntu Bionic):
status: New → Invalid
Balint Reczey (rbalint) wrote :

Sorry, it may be a valid bug, but may need more triaging.

Changed in systemd (Ubuntu Bionic):
status: Invalid → New
Changed in systemd (Ubuntu Focal):
status: Invalid → New
Changed in systemd (Ubuntu Groovy):
status: Invalid → New
Balint Reczey (rbalint) wrote :

So far this was unreproducible in an armhf lxc container running on arm64 host.
Do you have a reproducer for Ubuntu Classic?

Balint Reczey (rbalint) wrote :

BTW does it work in Core 20?

Changed in systemd (Ubuntu Focal):
status: New → Incomplete
Changed in systemd (Ubuntu Bionic):
status: New → Incomplete
Changed in systemd (Ubuntu Groovy):
status: New → Incomplete
Oliver Grawert (ogra) wrote :

i dont know where you guys track core bugs either since foundations took over the responsibility Ubuntu Core with core 18...

i can not reproduce it on classic anywhere but on each core18 image i have running at my house ...

the customer that initially reported it uses core18, so it is important to get it fixed there, regardless if it works in core 20 (i'll do some testing though, but i currently do not have any core20 installs around).

it is likely just core specific (confinement, the different way of assembling the rootfs or the fact that timedatectl has a wrapper on core)

Oliver Grawert (ogra) wrote :

theer we go ... thanks a lot dimitri, i opened

https://github.com/snapcore/core18/issues/157

Dimitri John Ledkov (xnox) wrote :

Also in core, timedatectl is a wrapper shell script, instead of the real one. So, some things that work regular timedatectl may not work with the one in the code. For example timezone name mangling / changes.

Also units are moved around a lot, such that things are not "enabled" via symlinks in /etc, but in /lib.

So yeah, ideally bugs about core should go first into the core* projects, as they are very different from classic file layout.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.