If DHCPv6 server is not responding, some times dhcp client process terminates with an error 'impossible condition reached'
If the DHCPv6 server is not responding, some of times dhcp client process terminates with an error 'impossible condition reached' and results in not releasing/clearing previously acquired DHCP IP address and other DHCP attributes.
This issue is seen only when the Dhcp server is not available and Dhcp ip address’s lease is expired at the Dhcp client side.
Some times dhclientv6 process stops with an error “Impossible condition at dhc6.c:318” during rebind time (when rebind interval is reaching zero) and results in not generating Dhcp release event.
This is an issue with ISC DHCP package of IPv6 dhcp client module.
What is expected : Dhcp client should not get terminated during rebind6 event if DHCPv6 server is not available. Instead dhcp client should release the ip address and start with solicit message