Opened 9 years ago

Closed 9 years ago

#807 closed enhancement (wontfix)

Improve error message when unknown type encountered

Reported by: stephen Owned by:
Priority: high Milestone: Sprint-20110419
Component: b10-auth Version:
Keywords: Cc:
CVSS Scoring: Parent Tickets:
Sensitive: no Defect Severity:
Sub-Project: Feature Depending on Ticket:
Estimated Difficulty: 2.0 Add Hours to Ticket: 0
Total Hours: 0 Internal?: no

Description

The current error message is rather cryptic.

Subtickets

Change History (4)

comment:1 Changed 9 years ago by stephen

  • Estimated Difficulty changed from 0.0 to 2

comment:2 Changed 9 years ago by shane

  • Milestone changed from Year 3 Task Backlog to Sprint-20110419
  • Priority changed from major to critical

comment:3 Changed 9 years ago by jinmei

What does this mean?

comment:4 Changed 9 years ago by jreed

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

I am closing this. The description here is too vague. And I am pretty sure the initial argument was misunderstood.

From jabber on March 25 (while in our meeting):

(05:13:04) jreed: Error loading database: database is locked
(05:13:35) jreed: is what was reported; that is the bigger issue. There was a new
 ticket created for that.
(05:13:48) jreed: The unclear error never even got shown due to the bigger issue.
(05:14:55) jreed: And jinmei already provided a patch to fix that too.
(05:16:13) jelte@jabber.isc.org: the actual error from b10-loadzone is much
 clearer than what came by on the list, btw
(05:16:24) jreed: Yes, definitely.
(05:16:34) jelte@jabber.isc.org: Error loading database: Error while loading
 tjeb.nl.: Cannot parse RR: tjeb.nl. 3600 IN AXEE ext.ns.whyscream.net.
(05:16:43) jreed: Exactly. That is clear. :)
(05:16:45) jelte@jabber.isc.org: so the problem may not even exist indeed :)
(05:16:54) jelte@jabber.isc.org: but i saw something like 'parameter error'
(05:17:19) jreed: loadzone is broken as it is.
(05:17:29) jelte@jabber.isc.org: it could be a *little* bit clearer if it said
 that it's not 'just' a parse error but really an unsupported type, but oh well

Let's ignore this for now. It is not critical and we don't want to keep wasting time on loadzone -- unless we re-decide to keep existing loadzone. (Note we need to use the pydnspp for our new loadzone.)

Note: See TracTickets for help on using tickets.