BIND 10 #1882: lettuce tests using port 53
BIND 10 Development
do-not-reply at isc.org
Tue Apr 10 19:06:57 UTC 2012
#1882: lettuce tests using port 53
-------------------------------------+-------------------------------------
Reporter: jreed | Owner:
Type: defect | Status: new
Priority: very low | Milestone: New
Component: Unclassified | Tasks
Sensitive: 0 | Keywords:
Sub-Project: DNS | Defect Severity: N/A
Estimated Difficulty: 0 | Feature Depending on Ticket:
Total Hours: 0 | Add Hours to Ticket: 0
| Internal?: 0
-------------------------------------+-------------------------------------
See tests/lettuce/configurations/example.org.config -- it has a Resolver
component but no configuration so results in:
{{{
2012-04-10 12:41:15.897 INFO [b10-boss.boss] BIND10_SOCKET_GET requesting
socket [::1]:53 of type TCP from the creator
2012-04-10 12:41:15.898 ERROR [b10-boss.boss] BIND10_SOCKET_ERROR error on
bind call in the creator: 13/Permission denied
2012-04-10 12:41:15.906 ERROR [b10-resolver.server_common]
SRVCOMM_ADDRESS_FAIL failed to listen on addresses ("Error creating socket
on bind")
2012-04-10 12:41:15.906 ERROR [b10-resolver.resolver]
RESOLVER_CONFIG_ERROR error in configuration: "Error creating socket on
bind"
2012-04-10 12:41:15.906 INFO [b10-resolver.resolver] RESOLVER_STARTED
resolver started
}}}
The tests/lettuce/features/example.feature Scenario: A simple example
uses that configuration but doesn't test resolver itself.
The Scenario: Removing modules test doesn't check for " bind10
module Resolver should be running".
I don't see any test uses of example.org.config that use the resolver.
This defect isn't important, but maybe the system level test should not
use port 53. (If had permission would enable a temporary internet server.)
--
Ticket URL: <http://bind10.isc.org/ticket/1882>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list