Univention Bugzilla – Bug 46697
4.3.0 DHCP failover stop working after upgrade
Last modified: 2018-04-13 13:40:24 CEST
Hello, i have DHCP failover configuration based on Univention and https://kb.isc.org/article/AA-00502/31 documentation. It works on 4.2.3 but don't work after 4.3 upgrade. /var/log/syslog: ``` failover peer dc: I move from recover to startup Mar 19 12:24:59 dc1 dhcpd[24832]: failover peer declaration with no referring pools. Mar 19 12:24:59 dc1 dhcpd[24832]: In order to use failover, you MUST refer to your main failover declaration Mar 19 12:24:59 dc1 dhcpd[24832]: in each pool declaration. You MUST NOT use range declarations outside Mar 19 12:24:59 dc1 dhcpd[24832]: of pool declarations. Mar 19 12:24:59 dc1 dhcpd[24832]: Mar 19 12:24:59 dc1 dhcpd[24832]: If you think you have received this message due to a bug rather Mar 19 12:24:59 dc1 dhcpd[24832]: than a configuration issue please read the section on submitting Mar 19 12:24:59 dc1 dhcpd[24832]: bugs on either our web page at www.isc.org or in the README file Mar 19 12:24:59 dc1 dhcpd[24832]: before submitting a bug. These pages explain the proper Mar 19 12:24:59 dc1 dhcpd[24832]: process and the information we find helpful for debugging.. ``` I checked all configuration . they are the same as on my production 4.2.3 version. ``` root@dc1:~# cat /etc/dhcp/local.conf # This can be used to modify local DHCP configuration options failover peer "dc" { primary; address dc1.xxxxx.localnet; port 519; peer address dc2.xxxxx.localnet; peer port 520; max-response-delay 60; max-unacked-updates 10; mclt 3600; split 128; load balance max seconds 3; } authoritative; ddns-update-style none; ```
root@dc1:~# udm dhcp/pool list DN: cn=xxxxx-pool,cn=192.168.1.0,cn=xxxxx.localnet,cn=dhcp,dc=xxxxx,dc=localnet all_clients: None dynamic_bootp_clients: deny failover_peer: dc known_clients: None name: xxxxx-pool range: 192.168.1.50 192.168.1.200 unknown_clients: None univentionPolicyReference: cn=default-settings,cn=boot,cn=dhcp,cn=policies,dc=xxxxx,dc=localnet univentionPolicyReference: cn=default-settings,cn=dns,cn=dhcp,cn=policies,dc=xxxxx,dc=localnet univentionPolicyReference: cn=xxxxxc,cn=leasetime,cn=dhcp,cn=policies,dc=xxxxxxx,dc=localnet
and additional in syslog: Mar 19 15:25:09 dc1 dhcpd[17818]: No subnet declaration for docker0 (172.17.42.1). Mar 19 15:25:09 dc1 dhcpd[17818]: ** Ignoring requests on docker0. If this is not what Mar 19 15:25:09 dc1 dhcpd[17818]: you want, please write a subnet declaration Mar 19 15:25:09 dc1 dhcpd[17818]: in your dhcpd.conf file for the network segment Mar 19 15:25:09 dc1 dhcpd[17818]: to which interface docker0 is attached. **
Known defect - will be fixed through Bug #46607 *** This bug has been marked as a duplicate of bug 46607 ***