BIND 10 #626: unexpected response from bind10 (SERVFAIL from auth server) (hotcache issue)
BIND 10 Development
do-not-reply at isc.org
Fri Mar 11 22:35:30 UTC 2011
#626: unexpected response from bind10 (SERVFAIL from auth server) (hotcache
issue)
-------------------------------------+-------------------------------------
Reporter: shane | Owner: jinmei
Type: defect | Status: reviewing
Priority: | Milestone: A-Team-
critical | Sprint-20110316
Component: | Resolution:
b10-auth | Sensitive: 0
Keywords: | Add Hours to Ticket: 0
Estimated Number of Hours: 5.0 | Total Hours: 0
Billable?: 1 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jinmei):
Replying to [comment:15 vorner]:
> > Holding merge until we get confirmation? In this case since we can
> > reproduce the problem and should be quite confident about the cause
> > and fix, I don't think we have to wait. But we should notify the
> > original reporter about the fix when we merge the fix to master.
>
> No, I don't want to wait with merge. I only asked if we want to wait
with closing the ticket (which is different matter than merging). But we
might as well close it and let it be reopened in case it doesn't work.
>
> Anyway, as I was saying, this can be merged.
Okay, thanks for review.
I don't have a strong opinion about close or keep open, but I'd be
inclined to close it in terms of task size estimation/evaluation (i.e,
if we required confirmation from the original reporter the duration
may be unnecessarily longer due to a reason we cannot control). If it
turns out that the initial fix doesn't really solve the original
problem I'd open a new ticket as a separate task (or reopen the
existing one with a revised estimation).
So, at the moment, I'll close the ticket (merge already done).
--
Ticket URL: <https://bind10.isc.org/ticket/626#comment:16>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list