[17:26] <znf> Does anyone have any tips on actually getting `network.service` work on Ubuntu 22.04? Our VPS system requires the use of /etc/network/interfaces (as it creates it upon start/deployment), and 22.04.1 seems to have worked just fine, but now with 22.04.3, network.service soft-fails -- it will delay a reboot by ~2 minutes, and the service shows up in a failed state
[17:26] <znf> the configuration *does* work tough 
[17:27] <znf> the message I'm getting is: https://pastie.dev/501IqO.yaml
[18:16] <ChmEarl> znf, dpkg -S '*/networking.service' -> ifupdown: /lib/systemd/system/networking.service
[18:16] <ChmEarl> ^ I ran that on Debian
[18:25] <ChmEarl> znf systemctl list-unit-files | grep net  <-- any networkd ?
[18:25] <ChmEarl> if so, mask it
[18:29] <ChmEarl> bottom line: /etc/network/interfaces is owned by package ifupdown, which uses networking.service
[18:34] <patdk-lap> I dont even have ifupdown installed on any of my systems
[18:48] <znf> ChmEarl, yeah, except there's something that sets up my interfaces _before_ networking.service
[18:48] <znf> and I have absolutely no idea _what_ 
[18:49] <znf> I disabled networking.service, systemd-networkd
[18:51] <znf> but it seems that systemd-networkd.service gets activated by the socket
[18:52] <znf> which brings up the interfaces _before_ networking.service
[18:52] <znf> and networking.service fails
[18:52] <znf> now overall this wouldn't have been such a big deal
[18:53] <znf> but this causes nnetwork-online.target to fail
[18:53] <znf> and thus... other services that might depend on that
[19:01] <frickler> check networkd-dispatcher.service , I had to disable that, too
[19:02] <znf> it's dead and disabled
[19:02] <znf> didn't really change anything
[19:06] <znf> https://pastie.dev/8zUUvP.yaml
[19:06] <znf> that's all there is in journalctl 
[19:11] <frickler> did you just disable or mask systemd-networkd?
[19:11] <znf> I disabled it
[19:11] <znf> but let's try masking it
[19:11] <znf> nope, still got network
[19:12] <znf> https://pastie.dev/i4wlWC.yaml
[19:14] <znf> perhaps ifup@eth0...
[19:14] <znf> why would this be enabled
[19:14] <znf> why is this a unit 
[19:14] <znf> why
[19:17] <znf> ok, so ifup@eth0 does the start, once I masked that, it no longer brings it up
[19:17] <znf> _but_
[19:17] <znf> networking.service is still not working
[22:17] <znf> Is there a list of stuff that a "minimized" 22.04 server install removes/does?
[22:17] <znf> I just noticed there's no /var/log/wtmp and such