NSD4 commands fails with new worker model+notify

Bug #1686060 reported by Dag Stenstad on 2017-04-25
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Tim Simmons

Bug Description

The worker.tasks.zone logic issues a notify to a pools target.host/target.port. The NSD4 backend has target.host/target.port set to the NSD Control service.

I've added the options "nsdc_host" and "nsdc_port" to my local impl_nsd4.py and pool, and things now seem to work again.

Ofcourse, this will probably break existing deployments. Maybe default nsdc_host/nsdc_port to host/port?

Tim Simmons (timsim) wrote :

I'll give this a look when I have a minute.

Changed in designate:
assignee: nobody → Tim Simmons (timsim)
status: New → Confirmed
importance: Undecided → Medium
tags: added: low-hanging-fruit
Tim Simmons (timsim) wrote :

Yeah the host/port there are used by the worker model to send notifies. The nsd backend should be moved to use a pattern similar to BIND with it's rndc host/port.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers