Opened 7 years ago

Closed 5 years ago

#2626 closed defect (wontfix)

lettuce timing failure for DDNS ACL

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 only one time out of six runs.

Scenario: ACL

# features/ddns_system.feature:89


A query for should have rcode NXDOMAIN # features/terrain/


AssertionError?: Expected: NXDOMAIN, got NO_ANSWER

Here is some stderr output that may be related (but I am not sure):

2013-01-10 15:19:22.774 DEBUG [b10-zonemgr.zonemgr/2025] ZONEMGR_LOAD_ZONE loading zone (class IN)
2013-01-10 15:19:22.776 WARN  [b10-zonemgr.zonemgr/2025] ZONEMGR_NO_SOA zone (class IN) does not have an SOA record
2013-01-10 15:19:22.776 DEBUG [b10-zonemgr.zonemgr/2025] ZONEMGR_STARTED zonemgr started
2013-01-10 15:19:26.273 DEBUG [b10-zonemgr.zonemgr/2025] ZONEMGR_REFRESH_ZONE refreshing zone (class IN)
2013-01-10 15:19:26.858 ERROR [b10-ddns.ddns/2029] DDNS_START_FORWARDER_FAIL Error sending request for DDNS UPDATE forwarding to b10-auth: recv() on cc session timed out
2013-01-10 15:19:26.858 INFO  [b10-ddns.ddns/2029] DDNS_STARTED ddns server is running and listening for updates
2013-01-10 15:19:27.224 DEBUG [] CC_GROUP_RECEIVE trying to receive a message
2013-01-10 15:19:31.225 ERROR [] CC_ASYNC_READ_FAILED asynchronous read failed (error code = 125)
2013-01-10 15:19:31.225 FATAL [b10-auth.auth/2026] AUTH_SERVER_FAILED server failed: asynchronous read failed
2013-01-10 15:19:31.226 INFO  [b10-auth.auth/2026] AUTH_DATASRC_CLIENTS_BUILDER_STOPPED data source builder thread stopped
2013-01-10 15:19:31.226 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 13: EOF
2013-01-10 15:19:31.227 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 10: EOF
2013-01-10 15:19:31.227 DEBUG [b10-auth.datasrc/2026] DATASRC_SQLITE_DROPCONN SQLite3Database is being deinitialized
2013-01-10 15:19:31.231 INFO  [b10-boss.boss/2007] BIND10_PROCESS_ENDED process 2026 of b10-auth ended with status 256
2013-01-10 15:19:31.231 ERROR [b10-boss.boss/2007] BIND10_COMPONENT_FAILED component b10-auth (pid 2026) failed: process exited normally with exit status 256
2013-01-10 15:19:31.231 FATAL [b10-boss.boss/2007] BIND10_COMPONENT_UNSATISFIED component b10-auth is required to run and failed
2013-01-10 15:19:31.238 INFO  [b10-xfrout.xfrout/2035] XFROUT_RECEIVED_SHUTDOWN_COMMAND shutdown command received
2013-01-10 15:19:31.242 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 6: <class 'OSError'>
2013-01-10 15:19:31.256 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 11: EOF
2013-01-10 15:19:31.259 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 14: EOF
2013-01-10 15:19:31.259 ERROR [b10-msgq.msgq/2011] MSGQ_RECV_ERR Error reading from socket 15: EOF
2013-01-10 15:19:32.239 INFO  [b10-boss.boss/2007] BIND10_PROCESS_ENDED process 2008 of Socket creator ended with status 0
2013-01-10 15:19:32.244 INFO  [b10-ddns.ddns/2029] DDNS_SHUTDOWN ddns server shutting down
2013-01-10 15:19:32.250 ERROR [b10-ddns.ddns/2029] DDNS_UNCAUGHT_EXCEPTION uncaught exception of type ConnectionResetError: [Errno 104] Connection reset by peer
2013-01-10 15:19:32.336 INFO  [b10-boss.boss/2007] BIND10_RECEIVED_SIGNAL received signal SIGTERM


Change History (3)

comment:1 Changed 7 years ago by jwright

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

comment:2 Changed 6 years ago by tomek

  • Milestone set to Remaining BIND10 tickets

comment:3 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.