BIND 10 #3384: Manual testing of Kea for 0.8 (BIND10 1.2) release.

BIND 10 Development do-not-reply at isc.org
Thu Apr 3 18:07:36 UTC 2014


#3384: Manual testing of Kea for 0.8 (BIND10 1.2) release.
-------------------------------------+-------------------------------------
            Reporter:  marcin        |                        Owner:
                Type:  task          |  marcin
            Priority:  high          |                       Status:
           Component:  dhcp          |  accepted
            Keywords:                |                    Milestone:  DHCP-
           Sensitive:  0             |  Kea0.9-alpha
         Sub-Project:  DHCP          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by tmark):

 4/3/2014
 {{{
 Manual testing of bind10 1.2 release candidate:

 Kea was run on Centos 6.4:
   - Builds fine with both mysql and pgsql config switches on at the same
 time.
   - All unit tests pass cleanly
   - Unit tests passed for entire bind10
   - Unit tests with valgrind on  dhcp4,dhcp6,d2,dhcpsrv were all clean.

 Basic testing with Kea4/D2, using postgresql backend.  Scapy was used to
 generate requests.  All requests had non-blank host name option.

 1. Kea4 configured with enable-updates off
     Was able to grand and release leases without issue

 2. Kea4 configured with enable-udpates on
    D2 configured with:

    a. Forward and reverse domains but none that match request:

         Outcome is correct:
         - Leases can be granted and released
         - NCRs are generated
         - D2 logs errors and discards the requests

    b. No domains defined:

         Outcome is correct:
         - Leases can be granted and released
         - NCRs are generated
         - D2 logs debug and discards the requests

    c. Matching fwd domain, no reverse domains, DNS server NOT running

         Outcome is correct:
         -Leases can be granted and released
         - NCRs are generated
         - D2 attempts forward, exhausts server list, reports error

    c. matching fwd domain, no reverse, server running

         Outcome is correct:
         - Lease granted and released
         - NCRs are generated
         - D2 processes forward DNS correctly, ingores reverse
         - DNS Server adds forward entries, then removes them

 Basic testing with Kea6/D2, using postgresql backend.  Scapy was used to
 generate the lease requests which all had Client FQDN option flag N=0,S=1

 1. Kea6 configured with enable-updates on

    D2 configured with:
     a. Matching forward and reverse domains but DNS server not running

         Outcome is correct:
         - Lease granted and released
         - NCRs are generated
         - D2 correctly matches forward and reverse servers  but exhausts
           servers on forward request, fails correctly

     b. Matching domains DNS server running

         Outcome is correct:
         - Lease granted and released
         - NCRs are generated
         - D2 processes forward and reverse DNS correctly
         - DNS Server adds forward entries, then removes them


 These tests required a fair amount b10-bindctl based configuration
 changes,
 all of which worked ok.

 I did find one small issue:

 Inadvertantly I attempted to release a lease that had already been
 released
 which exposed a missing log placeholder:

 2014-04-03 12:21:55.785 ERROR [b10-dhcp4.dhcp4/27012]
 DHCP4_RELEASE_EXCEPTION exception Missing logger placeholder in message:
 DHCP4_RELEASE_FAIL_NO_LEASE client (client-id hwtype=1 30:61:3a:30:62:3a)
 tried to release address 192.0.2.100, but there is no lease for such
 address. while trying to release address 0.0.0.0
 }}}

-- 
Ticket URL: <http://bind10.isc.org/ticket/3384#comment:2>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development


More information about the bind10-tickets mailing list