On Sat, Jun 7, 2025, at 14:16, Kevin P. Fleming wrote: > > I just upgraded to 2.6.3, and my network was broken because the daemons would > not start, because the configuration files placed the sockets in /tmp (which > is no longer permitted). > > While I understand that it's rare, if a patch release (incrementing only the > last component of the version number) contains breaking/incompatible changes, > please help the users by noting that in the release announcement. It is > certainly true that not every user reads the entirety of the release notes > before upgrading to a new version.
Taking this a step further... the reason my system was broken is that I had the sockets in /tmp, which was what all of the Kea example configurations included before 2.6.3 was released (the commits for the backport of the fixes to 2.6.3 changed the example configurations too). This definitely could have included a prominent warning, as all users who started with the example configurations and previously had no reason to change the socket paths will be required to change their configurations before upgrading.
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
