BIND 10 #2562: CC_TIMEOUT with no zonemgr when handling NOTIFY

BIND 10 Development do-not-reply at isc.org
Thu Mar 28 02:53:31 UTC 2013


#2562: CC_TIMEOUT with no zonemgr when handling NOTIFY
-------------------------------------+-------------------------------------
            Reporter:  jreed         |                        Owner:
                Type:  defect        |  jinmei
            Priority:  medium        |                       Status:
           Component:  b10-auth      |  reviewing
            Keywords:                |                    Milestone:
           Sensitive:  0             |  Sprint-20130402
         Sub-Project:  DNS           |                   Resolution:
Estimated Difficulty:  2             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:
                                     |  Medium
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------

Comment (by jinmei):

 Replying to [comment:12 pselkirk]:
 > Code changes look good, builds and tests fine, but I'm having trouble
 parsing the first sentence of the changelog.

 Thanks for the review.

 Regarding the changelog, I agree it wasn't readable.  How about this?
 {{{
 594.?   [bug]           jinmei
         b10-auth now handles the case where zonemgr isn't running while
         handling an incoming NOTIFY message separately from other general
         errors in the communication with zonemgr.  Previously both cases
         were logged at the error level, and resulted in increasing noise
         when zonemgr is intentionally stopped.  Other than the log level
         there is no change in externally visible behavior.
         (Trac #2562, git TBD)
 }}}

 And, I just realized I forgot to do one more thing in the branch:
 adding a lettuce (system) test.  And then it revealed the branch
 was actually buggy.  I should have explicitly set "want_answer" to
 true.  I've made these changes to the branch.  Could you review it?

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


More information about the bind10-tickets mailing list