Comment 6 for bug 1885901

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)