Description of problem:
message log is reporting "no matching state"

Version-Release number of selected component (if applicable):
4.2.0

How reproducible:
Consistent. Log prints error every 5 seconds.
Interval is set to "load balance max seconds 5"

Steps to Reproduce:
1.Run both primary and secondary dhcp servers
2.
3.
  
Actual results:
Jul  4 23:13:51 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:13:56 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:01 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:06 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:11 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:16 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:21 whitebox dhcpd: failover: listener: no matching state
Jul  4 23:14:26 whitebox dhcpd: failover: listener: no matching state


Expected results:


Additional info:
Primary server config:
failover peer "dhcp-failover" {
  primary;
  address 172.16.0.3;
  port 647;
  peer address 172.16.0.4;
  peer port 647;
  max-response-delay 60;
  max-unacked-updates 10;
  load balance max seconds 5;
  mclt 1800;
  split 128;
}

Secondary server config:
failover peer "dhcp-failover" {
  secondary;
  address 172.16.0.4;
  port 647;
  peer address 172.16.0.3;
  peer port 647;
  max-response-delay 60;
  max-unacked-updates 10;
  load balance max seconds 5;
  mclt 1800;
}



Servers have no firewall and SELinux is disabled. DHCP is functioning but constant log entries are a problem