kea-dhcp6 now correctly determines DNS update flags when
the allocation engine dynamically re-selects the lease's
network
Added ChangeLog entry
src/bin/dhcp6/dhcp6_srv.*
Dhcpv6Srv::assignLeases() removed response parameter from calls that no
longer need it
Dhcpv6Srv::processClientFqdn() - now sets the context DNS direction flags
Dhcpv6Srv::assignIA_NA()
Dhcpv6Srv::extendIA_NA() - no longer set context DNS direction flags, removed
now unused response parameter
Dhcpv6Srv::assignIA_PD() - removed unused response parameter
src/bin/dhcp6/tests/fqdn_unittest.cc
TEST_F(FqdnDhcpv6SrvTest, ddnsSharedNetworkTest) - now verifies lease DNS flags
TEST_F(FqdnDhcpv6SrvTest, ddnsSharedNetworkTest2) - new test to cover broken
scenario
src/lib/http/client.cc
ConnectionPool::Destination::pushRequest() - emits
a warning if the queue size has exceeded its threshold
src/lib/http/http_messages.mes
HTTP_CLIENT_QUEUE_SIZE_GROWING - new log message
A server in the partner-down state may transition to the waiting state and
synchronize its database when partner informs that it has allocated some
leases for which it did not send lease updates. Otherwise, the server
transitions to the normal state.
Previously, we'd assume that the communication with the partner is ok
when lease update was sent successfuly. In that case, we'd not send a
heartbeat. Under a heavy load, we could delay heartbeats for a long time.
Sending heartbeats is actually important because the heartbeat response
conveys information about the partner state. We want to have up-to-date
information about partner's state.
The server in the partner-down state seeing its parter in the hot-standby
state would remain in the current state until the partner transitions to
the waiting state. Previously, the server in the partner-down state could
transition to the hot-standby state causing the partner to not synchronize
its database.
A server finishing the lease database synchronization sends the
ha-sync-complete-notify command to the partner. If the partner is in the
partner-down state it stops allocating leases and sends a heartbeat to
see if the partner is available. If the partner is unavailable, it resumes
DHCP service. Otherwise, it transitions to the normal operation state.
Removed inserting dhcp client class from host manager. Previously, the
host manager would set dhcp_client_class column to an empty string causing
a referential integrity error with client classes. The column is now set
to null by default.
