Unfortunately I have already restored the VM back to a snapshot as it's semi-critical to operations, but I did take another snapshot of the storage prior to the rollback. Let me see if I can mount that and retrieve the logs to assist, I'll update as soon as I can grab them (or if I can't).
During the upgrade process I was definitely asked about the "new" packages having different config and given the opportunity to replace/keep/etc, and I chose keep in every instance after reviewing the diffs (the vast majority of the changes were just comments, or commented-out options). Given this, I'm a little confused about how the final system (post-reboot) wound up without the systemd unit files or binaries installed. I had to issue an "apt install freeradius" before I could even attempt to start the service, and it wouldn't start with a complaint about the config directory (/etc/freeradius/3.0/) being inaccessible (which makes sense when comparing it to permissions on a functional 22.04 system). This is technically a "point-release" change in freeradius -- from 3.0.x in Jammy to 3.2.x in Noble. I'll admit that I didn't review anything with Freeradius directly which I probably should've, I'm not sure if their config structure has changed significantly between versions. But again, my expectation was that Ubuntu would raise a flag if this was a problem rather than leaving me with a non-functional package. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2155090 Title: Upgrading 22.04LTS to 24.04LTS completely breaks freeradius To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freeradius/+bug/2155090/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
