bind9 does not log useful information

Bug #1359912 reported by Harm Weites
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Won't Fix
Medium
Unassigned

Bug Description

Using the bind9 backend and a wrong nzf path setting results in HTTP/500 messages without any clear reason. Logging needs improvement on this end.

Furthermore, nzf files and zones are beeing created just fine. Even if the initial request terminated with an error (500), trying to re-add a domain after having resolved the configuration issue now hits the client with yet another error: the domain already exists - even without ever returning a 200. Issueing a domain-list also returns an empty list.

Changed in designate:
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Harm Weites (harmw) wrote :

Ok, let me add this all originates in putting the nzf_path in the wrong section in the configurationfile. Designate should properly log that it couldn't find the nzf file in the specified location.

Revision history for this message
Graham Hayes (grahamhayes) wrote :

This is no longer valid with the new Bind9 backend (we don't use nzf files in Kilo)

Changed in designate:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.