Version: 246

Originally filed downstream as https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967906

resolvconf ships the following files

resolvconf: /lib/systemd/system/resolvconf-pull-resolved.path
resolvconf: /lib/systemd/system/resolvconf-pull-resolved.service

Those monitor changes to /run/systemd/resolve/stub-resolve.conf to update the resolvconf state accordingly. With 246, systemd enters a busy loop where it continously starts resolvconf-pull-resolved.service

To reproduce the problem, make sure resolved is enabled and active then create those two unit files

# cat test.service
[Unit]
Description=test

[Service]
Type=oneshot
ExecStart=sh -c 'date'

# cat test.path
[Path]
PathChanged=/run/systemd/resolve/stub-resolv.conf
PathExists=/run/systemd/resolve/stub-resolv.conf

Now start test.path and systemd, journald and dbus will hog the CPU trying to contiously start test.service