designate "could not find pool"

Bug #1881280 reported by BN
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
kolla-ansible
New
Undecided
Unassigned

Bug Description

**Environment**:
* OS (e.g. from /etc/os-release): Ubuntu 18.04
* Kernel (e.g. `uname -a`): 5.4.26-050426-generic
* Docker version if applicable (e.g. `docker version`): 19.03.9
* Kolla-Ansible version (e.g. `git head or tag or stable branch` or pip package version if using release): stable/ussuri
* Docker image Install type (source/binary): source
* Docker image distribution: centos
* Are you using official images from Docker Hub or self built? official images
* Share your inventory file, globals.yml and other configuration files if relevant

```
---
# You can use this file to override _any_ variable throughout Kolla.
# Additional options can be found in the
# 'kolla-ansible/ansible/group_vars/all.yml' file. Default value of all the
# commented parameters are shown here, To override the default value uncomment
# the parameter and change its value.
kolla_base_distro: "centos"
kolla_install_type: "source"
openstack_release: "ussuri"
kolla_internal_vip_address: "10.0.1.5"
network_interface: "enp2s0f0"
neutron_external_interface: "enp2s0f1"
enable_neutron_provider_networks: "yes"
neutron_tenant_network_types: "vxlan,flat"
enable_barbican: "yes"
enable_cinder: "yes"
enable_cinder_backup: "yes"
enable_designate: "yes"
dns_interface: "enp2s0f0"
designate_ns_record: "sample.openstack.org"
designate_backend: "bind9"
enable_redis: "yes"
enable_zun: "yes"
enable_kuryr: "yes"
enable_etcd: "yes"
enable_manila_backend_cephfs_native: "yes"
enable_manila: "yes"
docker_configure_for_zun: "yes"
containerd_configure_for_zun: "yes"
enable_ceph_rgw_keystone: "yes"
enable_ceph_rgw: "yes"
enable_magnum: "yes"
enable_octavia: "yes"
enable_heat: "yes"
ceph_nova_keyring: "ceph.client.nova.keyring"
magnum_tag: "master"
#horizon_tag: "master"
heat_tag: "master"
#designate_tag: "master"
#zun_tag: "master"
glance_backend_ceph: "yes"
cinder_backend_ceph: "yes"
nova_backend_ceph: "yes"
glance_enable_rolling_upgrade: "no"
barbican_crypto_plugin: "simple_crypto"
barbican_library_path: "/usr/lib/libCryptoki2_64.so"
horizon_port: 80
#octavia_loadbalancer_topology: "SINGLE"
#octavia_amp_boot_network_list: 21b56da9-3a1b-4b1b-8733-deed7708e4ec
#octavia_amp_secgroup_list: 235b1ef0-5a9c-409f-91a5-e8e70dd5dc00
#octavia_amp_flavor_id: 654e9269-db86-4038-8269-defd397ab694
```

Hey folks,

Designate is deployed, all containers are running fine, logs after deployment - http://paste.openstack.org/show/794143/

Bind9 container logs are fine as well - http://paste.openstack.org/show/794144/

Then I opened designate-worker and tried to update pool manually - http://paste.openstack.org/show/794145/ ; Pool Configuration is totally different to the one which is specified in pools.yaml file. Once you run update command - nothing is changed so it is looking for a pool which is not in pool config. Thus, not sure if its related to designate itself or k-a Update conf pool task is not working as it should.

Regards

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.