BIND 10 #2951: NXDOMAIN case at root server results in SERVFAIL w/ sqlite3 datasrc

[BIND 10 Development]

#2951: NXDOMAIN case at root server results in SERVFAIL w/ sqlite3 datasrc
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:  kean
                Type:  defect        |                       Status:
            Priority:  medium        |  reviewing
           Component:  data source   |                    Milestone:
            Keywords:                |  Sprint-20131015
           Sensitive:  0             |                   Resolution:
         Sub-Project:  DNS           |                 CVSS Scoring:
Estimated Difficulty:  0             |              Defect Severity:  N/A
         Total Hours:  0             |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by muks):

 * owner:  muks => kean


Comment:

 Hi Kean

 I made the port number the same as other tests as the branch would not
 pass lettuce tests without it.  This is because the terrain would try to
 query at the old port number unless this was merged to `master`.

 >  Running lettuce fails in one of your new tests:

 On my machine, the lettuce test passes in the branch that was put to
 review:
 {{{
   Scenario: Querying non-existing name in root zone from sqlite3 should
 work                                              #
 features/queries.feature:416
     Given I have bind10 running with configuration root.config
 # features/terrain/bind10_control.py:107
     And wait for bind10 stderr message BIND10_STARTED_CC
 # features/terrain/steps.py:34
     And wait for bind10 stderr message CMDCTL_STARTED
 # features/terrain/steps.py:34
     And wait for bind10 stderr message AUTH_SERVER_STARTED
 # features/terrain/steps.py:34
     bind10 module Auth should be running
 # features/terrain/bind10_control.py:334
     And bind10 module Stats should be running
 # features/terrain/bind10_control.py:334
     And bind10 module Resolver should not be running
 # features/terrain/bind10_control.py:334
     And bind10 module Xfrout should not be running
 # features/terrain/bind10_control.py:334
     And bind10 module Zonemgr should not be running
 # features/terrain/bind10_control.py:334
     And bind10 module Xfrin should not be running
 # features/terrain/bind10_control.py:334
     And bind10 module StatsHttpd should not be running
 # features/terrain/bind10_control.py:334
     A query for . type SOA should have rcode NOERROR
 # features/terrain/querying.py:206
     A query for nonexistent. type A should have rcode NXDOMAIN
 # features/terrain/querying.py:206
     Then wait for bind10 stderr message AUTH_SEND_NORMAL_RESPONSE not
 AUTH_PROCESS_FAIL                                   #
 features/terrain/steps.py:34
 }}}


 Did this lettuce failure happen after your modification of the port number
 in the branch?

 Can you attach the lettuce debug output and also the name of the failing
 test?

 From the snippet you have attached, `master` branch also has such similar
 errors, but these are on Mac OS for multi-auth feature:
 http://git.bind10.isc.org/~tester/builder/BIND10-lettuce/20140122120059-MacOSX10.6-x86_64-GCC/logs/lettuce.out

-- 
Ticket URL: <https://bind10.isc.org/ticket/2951#comment:3>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development