After upgrading 1.5.1 to rolling, isc-kea-dhcp6-server fails to start and DHCPv6 clients get no lease.
Rolling no longer creates the strongswan user (strongSwan 6, T8099/T9209), so every system user from uid 100 up moved down by one.
/config/dhcp/kea-dhcp6-serverid keeps its 1.5.1 owner, uid 101, which on rolling is zabbix instead of _kea.
$ systemctl is-active isc-kea-dhcp6-server failed kea-dhcp6: ERROR DHCP6_CONFIG_LOAD_FAIL ... unable to open DUID file /config/dhcp/kea-dhcp6-serverid for writing $ ls -ln /config/dhcp/kea-dhcp6-serverid -rw-r----- 1 101 102 ... /config/dhcp/kea-dhcp6-serverid
| user | uid on 1.5.1 | uid on rolling |
|---|---|---|
| strongswan | 100 | (gone) |
| _kea | 101 | 100 |
| zabbix | 102 | 101 |
| uuidd ... frr | 103 ... 109 | 102 ... 108 |
Only /config/dhcp is affected (checked all of /config after the upgrade). A fresh rolling install with the same config is not affected (server active, client gets a lease).
Suggested fix
src/init/vyos-router chowns /config/dhcp only when it creates it; chown it and its contents to _kea:vyattacfg on every boot.
Longer term, pin the uids of system users at image build.