Opened 7 years ago

Closed 5 years ago

#2627 closed defect (wontfix)

lettuce timing failure for ConfigManager

Reported by: jreed Owned by:
Priority: low Milestone: Remaining BIND10 tickets
Component: tests Version: bind10-old
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: N/A
Sub-Project: Core Feature Depending on Ticket:
Estimated Difficulty: 5 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no


Lettuce failure on CentOS 5.8 with python 3.3.0. This does not happen every time, but I saw it two times out of six runs.

Scenario: ACL

# features/ddns_system.feature:89


When I set DDNS ACL 0 for to REJECT # features/terrain/


AssertionError?: 'Error' was found in bindctl output:
Error: Module 'ConfigManager?' not responding
Configuration not committed

Exit from bindctl

The stderr output has:

2013-01-10 15:40:53.133 DEBUG [] CC_REPLY replying to message from '{ "from": "", "group": "Auth", "instance": "*", "seq": 15, "to": "*", "type": "send" }' with '{ "result": [ 0 ] }'
2013-01-10 15:40:53.133 DEBUG [] CC_START_READ starting asynchronous read
2013-01-10 15:40:53.133 DEBUG [b10-ddns.ddns/31358] DDNS_SESSION session arrived on file descriptor 11
2013-01-10 15:40:53.134 WARN  [b10-ddns.ddns/31358] DDNS_DROP_CONN dropping connection on file descriptor 11 because of error Receiving a forwarded FD failed: Connection reset by peer
2013-01-10 15:40:54.749 DEBUG [b10-zonemgr.zonemgr/31349] ZONEMGR_REFRESH_ZONE refreshing zone (class IN)
2013-01-10 15:40:57.131 ERROR [b10-cmdctl.cmdctl/31353] CMDCTL_COMMAND_ERROR error in command set_config to module ConfigManager: Module 'ConfigManager' not responding


Change History (4)

comment:1 Changed 7 years ago by jreed

Another run I hit the following for the same step:

AssertionError?: 'Error' was found in bindctl output:
Error: Timeout waiting for answer from DDNS
Configuration not committed

I don't see corresponding stderr logging for it trying to set the reject acl.

comment:2 Changed 7 years ago by jwright

  • Component changed from Unclassified to tests
  • Milestone changed from New Tasks to Next-Sprint-Proposed

comment:3 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:4 Changed 5 years ago by tomek

  • Resolution set to wontfix
  • Status changed from new to closed
  • Version set to old-bind10

This issue is related to bind10 code that is no longer part of Kea.

If you are interested in BIND10/Bundy framework or its DNS components,
please check

Closing ticket.

Note: See TracTickets for help on using tickets.