Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#1882 closed defect (invalid)

lettuce tests using port 53

Reported by: jreed Owned by:
Priority: very low Milestone: Sprint-20120417
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

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.)

Subtickets

Change History (2)

comment:1 Changed 8 years ago by muks

  • Resolution set to invalid
  • Status changed from new to closed

Closing as invalid, as this only happens on #1818's trac branch (the bug isn't in master).

The bug in #1818's trac branch is also gone.

comment:2 Changed 8 years ago by muks

  • Milestone changed from New Tasks to Sprint-20120417
Note: See TracTickets for help on using tickets.