BIND 10 #3157: The dhcp_srv_unittests fail when no network interface is configured

[BIND 10 Development]

#3157: The dhcp_srv_unittests fail when no network interface is configured
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:
  marcin                             |                Status:  new
                       Type:         |             Milestone:  DHCP
  defect                             |  Outstanding Tasks
                   Priority:         |              Keywords:
  medium                             |             Sensitive:  0
                  Component:  dhcp   |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 There are certain DHCP Srv unit tests that require at least one network
 interface to be configured with an address. Otherwise they fail because
 they can't find an appropriate interface to use for unit tests:

 {{{
 [ RUN      ] Dhcpv4SrvTest.processDiscover
 2013-09-04 18:32:18.837 DEBUG [bind10.dhcpsrv/31019]
 DHCPSRV_CFGMGR_DELETE_SUBNET4 deleting all IPv4 subnets
 2013-09-04 18:32:18.837 DEBUG [bind10.dhcpsrv/31019]
 DHCPSRV_CFGMGR_ADD_SUBNET4 adding subnet 192.0.2.0/24
 2013-09-04 18:32:18.837 DEBUG [bind10.dhcp4/31019] DHCP4_OPEN_SOCKET
 opening sockets on port 0
 2013-09-04 18:32:18.837 ERROR [bind10.dhcp4/31019]
 DHCP4_SRV_CONSTRUCT_ERROR error creating Dhcpv4Srv object, reason: No
 suitable interfaces for server-identifier found
 lt-dhcp4_unittests: /usr/include/boost/smart_ptr/shared_ptr.hpp:424: T*
 boost::shared_ptr<T>::operator->() const [with T = isc::dhcp::Option]:
 Assertion `px != 0' failed.
 /bin/sh: line 5: 31019 Aborted                 (core dumped) /bin/sh
 ../../../../libtool --mode=execute ${dir}$tst
 FAIL: dhcp4_unittests
 ===================================
 1 of 1 test failed
 Please report to bind10-dev at isc.org
 ===================================

 }}}

 One ofthe possible solutions proposed is to use the loopback interface for
 unit testing. Perhaps, it could be useful to update existing documentation
 with the information that the unit tests require at least one interface
 being configured to work properly.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3157>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development