It looks like the global need-reload state that Christian investigated that is being set by a snapd operation was added recently in systemd.
https://github.com/systemd/systemd/commit/a82b8b3dc80619c3275ad8180069289b411206d0
That is likely why we're only seeing this issue in noble.
From reading the commit message there, it sounds like the right thing to do is for snapd to issue a daemon-reload after it sets up all its units.
It looks like the global need-reload state that Christian investigated that is being set by a snapd operation was added recently in systemd.
https:/ /github. com/systemd/ systemd/ commit/ a82b8b3dc80619c 3275ad818006928 9b411206d0
That is likely why we're only seeing this issue in noble.
From reading the commit message there, it sounds like the right thing to do is for snapd to issue a daemon-reload after it sets up all its units.