Opened 8 years ago

Closed 8 years ago

#1293 closed defect (fixed)

ZONEMGR_UNKNOWN_ZONE_FAIL: Please submit a bug report.

Reported by: jreed Owned by: jelte
Priority: medium Milestone: Sprint-20120403
Component: Unclassified Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity: Medium
Sub-Project: DNS Feature Depending on Ticket:
Estimated Difficulty: 3 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

I did:

> Xfrin retransfer zone_name=foo master=a.b.c.d
"zone xfrin is started"

Where a.b.c.d was unreachable or didn't have data. (I knew it would fail.)

My bind10 logged:

2011-10-11 23:37:57.841 INFO  [b10-xfrin.xfrin] XFRIN_XFR_TRANSFER_STARTED AXFR transfer of zone foo./IN started
2011-10-11 23:37:58.011 INFO  [b10-xfrout.xfrout] XFROUT_AXFR_TRANSFER_FAILED transfer of foo./IN failed, rcode: SERVFAIL
2011-10-11 23:37:58.013 ERROR [b10-xfrin.xfrin] XFRIN_XFR_TRANSFER_FAILURE AXFR transfer of zone foo./IN failed: error response: SERVFAIL
2011-10-11 23:37:58.016 ERROR [b10-zonemgr.zonemgr] ZONEMGR_UNKNOWN_ZONE_FAIL zone foo. (class IN) is not known to the zone manager

or:

2011-10-11 23:42:02.468 ERROR [b10-xfrin.xfrin] XFRIN_CONNECT_MASTER error connecting to master at ('192.168.1.4', 53): [Errno 145] ETIMEDOUT
2011-10-11 23:42:02.471 ERROR [b10-zonemgr.zonemgr] ZONEMGR_UNKNOWN_ZONE_FAIL zone foo. (class IN) is not known to the zone manager

The message documentation has:

% ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager
An XFRIN operation has failed but the zone that was the subject of the
operation is not being managed by the zone manager.  This may indicate
an error in the program (as the operation should not have been initiated
if this were the case).  Please submit a bug report.

So here is the bug report.

Subtickets

Change History (10)

comment:1 Changed 8 years ago by shane

  • Defect Severity changed from N/A to Medium
  • Milestone changed from New Tasks to Year 3 Task Backlog

comment:2 Changed 8 years ago by jelte

  • Milestone changed from Year 3 Task Backlog to Next-Sprint-Proposed

comment:3 Changed 8 years ago by shane

This should be relatively simple to fix by adding a check for an empty zone, I think.

comment:4 Changed 8 years ago by vorner

I believe we should fix the description. If the command came from zonemgr, then this would be a bug. But as this is requested by user, the user simply made an error. We should explain that.

comment:5 Changed 8 years ago by jelte

  • Estimated Difficulty changed from 0 to 3

comment:6 Changed 8 years ago by jelte

  • Milestone changed from Next-Sprint-Proposed to Sprint-20120403

comment:7 follow-up: Changed 8 years ago by jelte

  • Owner set to UnAssigned
  • Status changed from new to reviewing

I think it's just that the command was originally not really intended for 'public' use, and the description of one of the error messages never got updated.

How's this?

% ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager
An XFRIN operation has failed but the zone that was the subject of the
operation is not being managed by the zone manager. This can be either the
result of a bindctl command to transfer in a currently unknown (or mistyped)
zone, or, if this error appears without the administrator giving transfer
commands, it can indicate an error in the program, as it should not have
initiated transfers of unknown zones on its own.

comment:8 in reply to: ↑ 7 Changed 8 years ago by jinmei

Replying to jelte:

I think it's just that the command was originally not really intended for 'public' use, and the description of one of the error messages never got updated.

How's this?

Looks good to me.

comment:9 Changed 8 years ago by jinmei

  • Owner changed from UnAssigned to jelte

comment:10 Changed 8 years ago by jelte

  • Resolution set to fixed
  • Status changed from reviewing to closed

Thanks, merged, closing ticket

Note: See TracTickets for help on using tickets.