Hi Dmitriy, I applied your patch manually to my OSA 23.2.0 environment and I deployed designate from scratch without any error on my Wallaby staging platform. I run the playbook a second time without any config change and it worked, and a third time with a small change in pools definition and it worked to. So, your patch looks good to me 😊 Thanks a lot ! JF
-----Original Message----- From: Dmitriy Rabotyagov <noonedeadpunk@gmail.com> Sent: vendredi, 25 novembre 2022 18:22 Cc: openstack-discuss@lists.openstack.org Subject: Re: [openstack-ansible] Designate: role seems trying to update DNS server pools before syncing database
EXTERNAL MESSAGE - This email comes from outside ELCA companies.
Hey,
That looks like a totally valid bug and regression has been introduced in Wallaby. I've just placed a patch that should cover this issue [1] and it would be awesome if you could test it.
[1] https://review.opendev.org/c/openstack/openstack-ansible- os_designate/+/865701
пт, 25 нояб. 2022 г. в 12:46, Taltavull Jean-François <jean-francois.taltavull@elca.ch>:
Hello,
During the first run, the playbook 'os-designate-install.yml' fails and the
'designate-manage pool update' command produces the log line below:
'Nov 25 11:50:06 pp3controller1a-designate-container-53d945bb designate-
manage[2287]: 2022-11-25 11:50:06.518 2287 CRITICAL designate [designate- manage - - - - -] Unhandled error: oslo_messaging.rpc.client.RemoteError: Remote error: ProgrammingError (pymysql.err.ProgrammingError) (1146, "Table 'designate.pools' doesn't exist")'
Looking at the 'os_designate' role code shows that the handler ` Perform
Designate pools update` is flushed before tables are created in the 'designate' database.
O.S.: Ubuntu 20.04 OpenStack release: Wallaby OSA tag: 23.2.0
Regards,
Jean-Francois