An update to the comment above. We have found out a sequence of commands
that seems to reproduce the issue reliably: in the spread session
started by the command from the comment above, if you type this:
systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
systemctl daemon-reload
# The two commands above are just to ensure that the unit is in the
unmounted state
systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
systemctl daemon-reload
systemctl stop 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
systemctl start 'snap-disabled\x2dsvcs\x2dkept-x1.mount'
The last command will hang for 90 seconds, after which the job will fail
and `journalctl -xe` will show that it failed because systemd timed out
while activating a loop device. In reality, the loop device is already
there and is available, but somehow the `deamon-reload` operation broke
the internal status.
If you remove the line with `systemctl daemon-reload` (or, on the other
hand, add one such line even after the `stop` command), then everything
proceeds normally. I'm EOD now, but tomorrow I'll verify if this happens
on classic too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1949089
Title:
systemd randomly fails to activate mount units in Ubuntu Core 18
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
