config option nameservers not clearing up old configuration data
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Triaged
|
Medium
|
Unassigned |
Bug Description
setting nameservers to some setting, it only creates the new zones. After changing the nameservers options to some new value, the charm does not remove the old options.
The expected behaviour would be to remove the old configuration from designate DB.
lib/charm/
with cls.check_
if hookenv.
$ juju config designate nameservers
ns1.testdomain.eu. ns2.testdomain.eu. ns3.testdomain.eu.
$ designate server-list
+------
| id | name |
+------
| 4436be7e-
| 5fd94f58-
| d1328565-
| 357570af-
| 249f1045-
+------
Changed in charm-designate: | |
importance: | Undecided → Medium |
status: | New → Triaged |
Hi @gabor can you specifc which release of openstack you hit this issue with? I ask because I think there are two issues in the charm, first is the one you hit i.e. old records not removed but with Rocky these don't get updated at all since the charm is hardcoded to use python- designateclient which is deprecated and hardwired to use the deprecated v1 api. Solution is to switch to python- openstackclient (or just use the api direct) and also use designate-maname [1]. I'll raise a seperate bug for the second issue.
[1] https:/ /docs.openstack .org/designate/ rocky/admin/ pools.html