BIND 10 #2743: regression due to #2145

[BIND 10 Development]

#2743: regression due to #2145
-------------------------------------+-------------------------------------
            Reporter:  jinmei        |                        Owner:
                Type:  defect        |  UnAssigned
            Priority:  medium        |                       Status:
           Component:  logging       |  reviewing
            Keywords:                |                    Milestone:  Next-
           Sensitive:  0             |  Sprint-Proposed
         Sub-Project:  Core          |                   Resolution:
Estimated Difficulty:  0             |                 CVSS Scoring:
         Total Hours:  0             |              Defect Severity:  N/A
                                     |  Feature Depending on Ticket:
                                     |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
Changes (by jinmei):

 * subproject:  DNS => Core


Old description:

> It turned out #2145 introduced a regression where cfgmgr initializes
> logging before loading datasrc module, leading to awkward log messages
> and lettuce failure:
> http://git.bind10.isc.org/~tester/builder/BIND10-lettuce/20130214190419-MacOSX10.6-x86_64-GCC/logs/lettuce.out
>
> A temporary workaround is to simply revert the change, and it was
> done in the trac2145-revert branch.
>
> Its urgency for master may be debatable.  While embarrassing, we can
> suppress it by running lettuce without specifying
> `--enable-logger-checks`, and by ignoring other awkward log messages.
>
> At the moment I'm just moving it to the review queue as a candidate
> task for the next sprint.

New description:

 It turned out #2145 introduced a regression where cfgmgr initializes
 logging before loading datasrc module, leading to awkward log messages
 and lettuce failure:
 http://git.bind10.isc.org/~tester/builder/BIND10-lettuce/20130214190419-MacOSX10.6-x86_64-GCC/logs/lettuce.out

 A temporary workaround is to simply revert the change, and it was
 done in the trac2145-revert branch.

 Its urgency for master may be debatable.  While embarrassing, we can
 suppress it by running lettuce without specifying
 `--enable-logger-checks`, and by ignoring other awkward log messages.
 (note also: if we complete #2746 we don't need the revert).

 At the moment I'm just moving it to the review queue as a candidate
 task for the next sprint.

--

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