Unable to add zone to Designate - "Could not find Pool"

Bug #1886321 reported by Valdemar Lemche
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kolla
Invalid
Undecided
Unassigned
kolla-ansible
New
Undecided
Unassigned

Bug Description

I'm deploying a all-in-one kolla environment on ubuntu 18.04.4 x86_64.

Immediately after I've deployed the kolla environment, I try to add a zone to finailze the Designate configuration according to the documentation. But I get the error "Could not find Pool" when trying so.

$ openstack zone create --email <email address hidden> os.se.lemche.net.
Could not find Pool

I've enabled debug = True in the relevant services before I deploy - i.e.

crudini --set /etc/kolla/config/designate.conf DEFAULT debug True
crudini --set /etc/kolla/config/neutron.conf DEFAULT debug True
crudini --set /etc/kolla/config/nova.conf DEFAULT debug True
crudini --set /etc/kolla/config/keystone.conf DEFAULT debug True

But I only see the following errors during deployment /var/log/kolla/designate/designate-manage.log:
2020-07-05 13:48:53.710 971 CRITICAL designate.manage.pool [designate-manage - - - - -] Bad ID Supplied for pool. pool_id: 28cfda3d-3f69-49bd-9bea-c7639cc59756 message: Could not find Pool
Traceback (most recent call last):

  File "/usr/lib/python3/dist-packages/designate/rpc.py", line 238, in exception_wrapper
    return f(self, *args, **kwargs)

  File "/usr/lib/python3/dist-packages/designate/central/service.py", line 2283, in get_pool
    return self.storage.get_pool(context, pool_id)

  File "/usr/lib/python3/dist-packages/designate/storage/impl_sqlalchemy/__init__.py", line 983, in get_pool
    return self._find_pools(context, {'id': pool_id}, one=True)

  File "/usr/lib/python3/dist-packages/designate/storage/impl_sqlalchemy/__init__.py", line 911, in _find_pools
    sort_dir)

  File "/usr/lib/python3/dist-packages/designate/sqlalchemy/base.py", line 250, in _find
    raise exc_notfound(msg)

designate.exceptions.PoolNotFound: Could not find Pool
: designate.exceptions_Remote.PoolNotFound_Remote: Could not find Pool

And when I try to create the zone, I see this in /var/log/kolla/designate/designate-api.log:
2020-07-05 14:03:20.051 969 DEBUG eventlet.wsgi.server [-] (969) accepted ('192.168.0.30', 42980) server /usr/lib/python3/dist-packages/eventlet/wsgi.py:985
2020-07-05 14:03:20.057 969 INFO eventlet.wsgi.server [-] 192.168.0.253,192.168.0.30 "GET / HTTP/1.1" status: 200 len: 303 time: 0.0037324
2020-07-05 14:03:20.616 969 DEBUG designate.objects.adapters.base [req-e7178dd0-6cd4-4d07-b96f-f44390aca575 ca9f270dbad74979af523dfc5ee68961 e7b468c310f245b3871f5178f7179844 - - -] Creating Zone object with values {'name': 'os.se.lemche.net.', 'type': '
PRIMARY', 'email': '<email address hidden>'} parse /usr/lib/python3/dist-packages/designate/objects/adapters/base.py:173
2020-07-05 14:03:20.617 969 DEBUG designate.objects.adapters.base [req-e7178dd0-6cd4-4d07-b96f-f44390aca575 ca9f270dbad74979af523dfc5ee68961 e7b468c310f245b3871f5178f7179844 - - -] <Zone id:'None' type:'None' name:'None' pool_id:'None' serial:'None' act
ion:'None' status:'None'> parse /usr/lib/python3/dist-packages/designate/objects/adapters/base.py:174
2020-07-05 14:03:20.763 969 INFO eventlet.wsgi.server [req-e7178dd0-6cd4-4d07-b96f-f44390aca575 ca9f270dbad74979af523dfc5ee68961 e7b468c310f245b3871f5178f7179844 - - -] 192.168.0.253,192.168.0.30 "POST /v2/zones HTTP/1.1" status: 404 len: 313 time: 0.7
020037

This is my globals.yml

(kolla) kolla@jack:~$ grep -v -E "^$|^#" /etc/kolla/globals.yml | sort
---
cinder_volume_group: "system"
designate_backend: "bind9"
designate_ns_record: "os.se.lemche.net"
enable_cinder_backend_lvm: "yes"
enable_cinder: "yes"
enable_designate: "yes"
enable_grafana: "yes"
enable_neutron_provider_networks: "yes"
enable_octavia: "yes"
enable_prometheus: "yes"
enable_redis: "yes"
kolla_base_distro: "ubuntu"
kolla_copy_ca_into_containers: "yes"
kolla_enable_tls_backend: "yes"
kolla_enable_tls_external: "yes"
kolla_enable_tls_internal: "yes"
kolla_external_fqdn: "openstack.se.lemche.net"
kolla_external_vip_address: "192.168.0.253"
kolla_install_type: "binary"
kolla_internal_fqdn: "openstack.se.lemche.net"
kolla_internal_vip_address: "192.168.0.253"
network_interface: "eno1"
neutron_external_interface: "bond0"
neutron_plugin_agent: "openvswitch"
node_custom_config: "/etc/kolla/config"
nova_compute_virt_type: "kvm"
openstack_cacert: "/etc/ssl/certs/ca-certificates.crt"
openstack_logging_debug: "False"
openstack_release: "master"
syslog_server: "192.168.0.40"
syslog_udp_port: "514"

Changed in kolla:
status: New → Invalid
Revision history for this message
LuuVuong (luuvuong) wrote :

Hi,

Please let me know away fix it

Thanks

Revision history for this message
JUAN MIGUEL GARCIA RETAMAR (agdelta) wrote :

The same case is happening to me, is there a solution?

This is my config

[user1@kolla]# cat globals.yml | grep -iv ^# | grep .
---
kolla_base_distro: "centos"
kolla_install_type: "binary"
openstack_release: "ussuri"
kolla_internal_vip_address: "172.18.0.40"
kolla_external_vip_address: "192.168.198.40"
network_interface: "bond0"
kolla_external_vip_interface: "enp33s0f0"
dns_interface: "enp33s0f0"
neutron_external_interface: "enp33s0f1"
keepalived_virtual_router_id: "52"
kolla_enable_tls_internal: "no"
kolla_enable_tls_external: "no"
kolla_verify_tls_backend: "no"
kolla_enable_tls_backend: "no"
enable_central_logging: "yes"
enable_chrony: "no"
enable_cinder: "yes"
enable_designate: "yes"
enable_elasticsearch: "yes"
enable_horizon_designate: "{{ enable_designate | bool }}"
enable_horizon_monasca: "yes"
enable_monasca: "yes"
monasca_install_type: "source"
enable_neutron_dvr: "yes"
enable_redis: "yes"
enable_skydive: "yes"
external_ceph_cephx_enabled: "yes"
ceph_glance_keyring: "ceph.client.glance.keyring"
ceph_glance_user: "glance"
ceph_glance_pool_name: "images"
ceph_cinder_keyring: "ceph.client.cinder.keyring"
ceph_cinder_user: "cinder"
ceph_cinder_pool_name: "volumes"
ceph_cinder_backup_keyring: "ceph.client.cinder-backup.keyring"
ceph_cinder_backup_user: "cinder-backup"
ceph_cinder_backup_pool_name: "backups"
ceph_nova_keyring: "{{ ceph_cinder_keyring }}"
ceph_nova_user: "cinder"
ceph_nova_pool_name: "vms"
glance_backend_ceph: "yes"
cinder_backend_ceph: "yes"
cinder_backup_driver: "ceph"
designate_backend: "bind9"
designate_ns_record: "lab.sample.com"
designate_coordination_backend: "{{ 'redis' if enable_redis|bool else '' }}"
nova_backend_ceph: "yes"

Revision history for this message
JUAN MIGUEL GARCIA RETAMAR (agdelta) wrote :

Solucionado con lo siguiente:

Desde el container; designate-worker, generar un dump de la configuración

- designate-manage pool generate_file --file ~/dump.yml

El fichero pools.yaml, comentar la linea del ID y ejecutar

- designate-manage pool update --delete --file /etc/designate/pools.yaml

luego poner el id que aparece en dump.yml en pools.yaml y volver a ejecutar

- designate-manage pool update --delete --file /etc/designate/pools.yaml

y ese mismo id llevarlo al kolla-ansible, al fichero password.yaml y actualizar el id

- designate_pool_id: 3679ea8f-b934-4c0f-b24e-3bc08fbee1b0

Y agregarlo tambien alfichero

- /config/designate/designate-sink.conf

[handler:nova_fixed]
zone_id = 3679ea8f-b934-4c0f-b24e-3bc08fbee1b0
[handler:neutron_floatingip]
zone_id = 3679ea8f-b934-4c0f-b24e-3bc08fbee1b0

y lanzar con reconfigure con los tags de designate, nova y neutron

- kolla-ansible reconfigure -i multinode --tags designate,neutron,nova

Revision history for this message
JUAN MIGUEL GARCIA RETAMAR (agdelta) wrote :
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.