Both designate and designate-bind charms are ignoring dns-backend binding
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Fix Released
|
Critical
|
Tytus Kurek | ||
OpenStack Designate-Bind Charm |
Fix Released
|
Undecided
|
Tytus Kurek | ||
charms.openstack |
Invalid
|
Critical
|
Tytus Kurek |
Bug Description
Designate (cs:~openstack-
juju deploy --series trusty --num-units 3 --bind "provisioning admin=openstack
juju deploy --series trusty --num-units 3 --bind "provisioning dns-backend=
tytus@maas:~$ cat designate.yaml
designate:
debug: "true"
enable-
openstack-origin: "cloud:
region: "Softlayer"
use-syslog: "true"
verbose: "true"
vip: "10.24.111.14 10.24.112.14 10.24.113.14"
tytus@maas:~$ cat designate-bind.yaml
designate-bind:
debug: "true"
use-syslog: "true"
verbose: "true"
in juju environment with the following spaces:
tytus@maas:~$ juju list-spaces
Space Subnets
openstack-admin 10.24.111.0/24
openstack-internal 10.24.112.0/24
openstack-public 10.24.113.0/24
provisioning 10.24.110.0/24
This results with the following files being created:
- on designate side:
root@juju-
- id: 794ccc2c-
name: default
description: Pool genergated by Juju
nameservers:
- host: 10.24.110.251
port: 53
- host: 10.24.110.203
port: 53
- host: 10.24.110.250
port: 53
targets:
- type: bind9
masters:
- host: 10.24.110.172
port: 5354
- host: 10.24.110.180
port: 5354
- host: 10.24.110.233
port: 5354
options:
rndc_host: 10.24.110.251
- type: bind9
masters:
- host: 10.24.110.172
port: 5354
- host: 10.24.110.180
port: 5354
- host: 10.24.110.233
port: 5354
options:
rndc_host: 10.24.110.203
- type: bind9
masters:
- host: 10.24.110.172
port: 5354
- host: 10.24.110.180
port: 5354
- host: 10.24.110.233
port: 5354
options:
rndc_host: 10.24.110.250
also_notifies:
- host: 10.24.110.251
port: 53
- host: 10.24.110.203
port: 53
- host: 10.24.110.250
port: 53
- on designate-bind side:
root@juju-
// This is the primary configuration file for the BIND DNS server named.
//
// Please read /usr/share/
// structure of BIND configuration files in Debian, *BEFORE* you customize
// this configuration file.
//
// If you are just adding zones, please do that in /etc/bind/
include "/etc/bind/
include "/etc/bind/
include "/etc/bind/
controls {
inet 10.24.110.251 allow { 10.24.110.
};
root@juju-
options {
directory "/var/cache/bind";
// If there is a firewall between you and nameservers you want
// to talk to, you may need to fix the firewall to allow multiple
// ports to talk. See http://
// If your ISP provided one or more IP addresses for stable
// nameservers, you probably want to use them as forwarders.
// Uncomment the following block, and insert the addresses replacing
// the all-0's placeholder.
// If BIND logs error messages about the root key being expired,
// you will need to update your keys. See https:/
recursion no;
};
As you can see all IPs belong to the 10.24.110.0/24 subnet ("provisioning" space), so the communication between designate and designate-bind uses this space instead of "openstack-
tags: | added: 4010 cpe-onsite |
Changed in charm-designate: | |
assignee: | nobody → Tytus Kurek (tkurek) |
Changed in charm-designate-bind: | |
assignee: | nobody → Tytus Kurek (tkurek) |
Changed in charm-designate: | |
status: | New → In Progress |
Changed in charm-designate-bind: | |
status: | New → In Progress |
Changed in charm-designate: | |
status: | Confirmed → In Progress |
Changed in charms.openstack: | |
assignee: | nobody → Tytus Kurek (tkurek) |
status: | Confirmed → In Progress |
Changed in charm-designate-bind: | |
status: | In Progress → Fix Committed |
Changed in charms.openstack: | |
status: | In Progress → Invalid |
Changed in charm-designate-bind: | |
milestone: | none → 17.11 |
Changed in charm-designate: | |
status: | Fix Committed → Fix Released |
Changed in charm-designate-bind: | |
status: | Fix Committed → Fix Released |
We recently fixed issues with the "external" bindings admin, internal and public. This DTRT for conical_url and resolve_address for use when publishing to the keystone catalog.
However, we are not handling arbitrary relations in reactive charms. charms.openstack needs something similar to or to use get_relation_ip in charmhelpers: /github. com/juju/ charm-helpers/ blob/master/ charmhelpers/ contrib/ network/ ip.py#L559
https:/
We need to support network_get calls with arbitrary relationship interface names, in this case, dns-backend.