# Stork 1.7.0, October 12th, 2022, Release Notes Welcome to Stork 1.7.0, another development release. The changes introduced in this version are: 1. **Nested DHCP options in host reservations**: Stork now allows three levels of DHCP options encapsulation when a new host reservation is created or an existing host reservation is updated. Preliminary support for standard DHCP option definitions has been added. A few standard DHCPv6 option definitions have been defined in Stork, allowing option fields returned by the Kea servers to be accurately recognized [#837]. 2. **HA data in troubleshooting dump**: The DHCP high availability (HA) state of Kea is now included in the troubleshooting dump tarball. This should make it easier to debug problems related to HA [#819]. 3. **Native package improvements**: A bug was fixed in the post-install hook when Stork was installed from packages on Debian with busybox. The package hooks now treat SystemD as an optional dependency. The Stork user is added to the Kea group by default, if present. Installation CI checks were added for all package types [#748, #860, #867, #869]. 4. **SIGHUP support**: The Stork server and agent now reload upon receiving the SIGHUP signal. This can be used on its own or by using `systemctl reload` if available [#703]. 5. **Bugfixes**: Stork no longer continuously produces false disconnect and reconnect events when Kea uses a host backend with RADIUS hook [#817]. A bug was fixed in the Stork server that caused stale HA services when the HA configuration was updated in Kea. It could sometimes result in showing an outdated HA status on the dashboard page [#818]. A bug was fixed on the application page that caused the wrong daemon tab selection [#722]. 6. **Documentation updates**: Configuration review usage is now described in the ARM [#847]. The Stork agent must trust the REST TLS certificate presented by the Stork server. Although using a proper, trusted certificate is recommended, a self-signed certificate can also be used. A detailed discussion can be found in the GitLab ticket [#859]. 7. **Development**: The Storybook framework has been integrated with the Stork build system for faster and easier UI development [#845]. Please see this link for known issues: https://gitlab.isc.org/isc-projects/stork/-/wikis/Known-issues. ## Incompatible Changes None. ## Release Model Stork has monthly development releases, with some exceptions. We encourage users to test the development releases and report back their findings on the stork-users mailing list, available at https://lists.isc.org/mailman/listinfo/stork-users. This text references issue numbers. For more details, visit the Stork GitLab page at https://gitlab.isc.org/isc-projects/stork/issues. ## License Stork is released under the Mozilla Public License, version 2.0. https://www.mozilla.org/en-US/MPL/2.0 ## Download The easiest way to install the software is to use native deb or RPM packages. They can be downloaded from: https://cloudsmith.io/~isc/repos/stork/ The Stork source and PGP signature for this release may be downloaded from: https://downloads.isc.org/isc/stork The signature was generated with the ISC code-signing key, which is available at: https://www.isc.org/pgpkey ISC provides documentation in the Stork Administrator Reference Manual (ARM). It is available on ReadTheDocs.io at https://stork.readthedocs.io/en/latest/, and in source form in [the doc/ directory](https://gitlab.isc.org/isc-projects/stork/-/tree/master/doc). We ask users of this software to please let us know how it worked for you and what operating system you tested on. Feel free to share your feedback on the stork-users mailing list (https://lists.isc.org/mailman/listinfo/stork-users). We would also like to hear whether the documentation is adequate and accurate. Please open tickets in the Stork GitLab project for bugs, documentation omissions and errors, and enhancement requests. We want to hear from you even if everything worked. ## Support Free best-effort support is provided by our user community via a mailing list. Information on all public email lists is available at https://www.isc.org/mailinglists/. If you have any comments or questions about working with Stork, please share them to the stork-users list (https://lists.isc.org/mailman/listinfo/stork-users). Bugs and feature requests may be submitted via GitLab at https://gitlab.isc.org/isc-projects/stork/issues. ## Changes The following summarizes changes and important upgrades since the Stork 1.6.0 release. * 248 [bug] slawek Fixed a bug continuously producing false disconnect and reconnect events when Kea used a host backend without support for listing (e.g., RADIUS). (Gitlab #817) * 247 [bug] slawek Fixed a bug in the post-install hook when Stork was installed from the packages on Debian with busybox. The package hooks now treat SystemD as an optional dependency. The Stork user is joined to the Kea group by default. Added installation CI checks for all package types. (Gitlab #749, #860, #867, #869) * 246 [func] marcin DHCP high availability state is included in the troubleshooting dump tarball. (Gitlab #819) * 245 [func] marcin Stork server and agent reload upon receiving the SIGHUP signal. (Gitlab #703) * 244 [bug] marcin Fixed a bug on the application page causing wrong daemon tab selection. (Gitlab #772) * 243 [doc] marcin Described the configuration review usage in the ARM. (Gitlab #847) * 242 [bug] marcin Fixed a bug in the Stork server causing stale HA services when the HA configuration has been updated in Kea. It could sometimes result in showing outdated HA status on the dashboard page. (Gitlab #818) * 241 [build] slawek Integrated Storybook framework with the Stork build system for faster and easier UI development. (Gitlab #845) * 240 [func] marcin Allow three levels of DHCP options encapsulation when a new host reservation is created or an existing host reservation is updated. Preliminary support for standard DHCP option definitions has been added. A few standard DHCPv6 option definitions have been defined in Stork, allowing to recognize option fields returned by the Kea servers accurately. (Gitlab #837) Thank you again to everyone who assisted us in making this release possible. We look forward to receiving your feedback.