Symptom: charm stuck in blocked state because of the service designate-agent failing
App Version Status Scale Charm Channel Rev Exposed Message
designate caracal blocked 1 designate latest/edge 224 no Services not running that should be: designate-agent
The service to be checked is defined as list in the code. Yet it should be handled for backward compatibility it should be removed from the list if the version is >= Caracal(2024.1)
I also see that the package still exist while it should be removed
ubuntu@juju-8a251a-6-lxd-0:~$ apt-cache policy show designate-agent
designate-agent:
Installed: 1:14.0.4-0ubuntu1
Candidate: 1:18.0.0-0ubuntu1~cloud0
Version table:
1:18.0.0-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/caracal/main amd64 Packages
Yet the actual binary used to be packaged as /usr/bin/designate-agent in python3-designate, while it is not now
ubuntu@juju-8a251a-6-lxd-0:~$ dpkg -L python3-designate|grep bin
/usr/bin
/usr/bin/designate-api
/usr/bin/designate-api-wsgi
/usr/bin/designate-central
/usr/bin/designate-manage
/usr/bin/designate-mdns
/usr/bin/designate-producer
/usr/bin/designate-rootwrap
/usr/bin/designate-sink
/usr/bin/designate-status
/usr/bin/designate-worker
/usr/lib/python3/dist-packages/designate/backend/impl_bind9.py
/usr/lib/python3/dist-packages/designate/tests/unit/backend/test_bind9.py
Symptom: charm stuck in blocked state because of the service designate-agent failing
App Version Status Scale Charm Channel Rev Exposed Message
designate caracal blocked 1 designate latest/edge 224 no Services not running that should be: designate-agent
The charm requires designate-agent service to be running, yet this one was removed in Caracal /docs.openstack .org/releasenot es/designate/ 2024.1. html
See the description:
https:/
>Designate-agent removal is complete in this version of designate.
The service to be checked is defined as list in the code. Yet it should be handled for backward compatibility it should be removed from the list if the version is >= Caracal(2024.1)
See the code excerpt here: /opendev. org/openstack/ charm-designate /src/branch/ master/ src/lib/ charm/openstack /designate. py#L314
https:/
I also see that the package still exist while it should be removed juju-8a251a- 6-lxd-0: ~$ apt-cache policy show designate-agent 0-0ubuntu1~ cloud0 18.0.0- 0ubuntu1~ cloud0 500 ubuntu- cloud.archive. canonical. com/ubuntu jammy-updates/ caracal/ main amd64 Packages
ubuntu@
designate-agent:
Installed: 1:14.0.4-0ubuntu1
Candidate: 1:18.0.
Version table:
1:
500 http://
This package contained auto-generated service: juju-8a251a- 6-lxd-0: ~$ dpkg -L designate-agent d/designate- agent system/ designate- agent.service doc/designate- agent doc/designate- agent/copyright doc/designate- agent/changelog .Debian. gz juju-8a251a- 6-lxd-0: ~$ apt-cache policy show python3-designate 0-0ubuntu1~ cloud0 0-0ubuntu1~ cloud0 0-0ubuntu1~ cloud0 500 ubuntu- cloud.archive. canonical. com/ubuntu jammy-updates/ caracal/ main amd64 Packages dpkg/status
ubuntu@
/.
/etc
/etc/init.d
/etc/init.
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/
/usr
/usr/share
/usr/share/doc
/usr/share/
/usr/share/
/usr/share/
ubuntu@
python3-designate:
Installed: 1:18.0.
Candidate: 1:18.0.
Version table:
*** 1:18.0.
500 http://
100 /var/lib/
Yet the actual binary used to be packaged as /usr/bin/ designate- agent in python3-designate, while it is not now juju-8a251a- 6-lxd-0: ~$ dpkg -L python3- designate| grep bin designate- api designate- api-wsgi designate- central designate- manage designate- mdns designate- producer designate- rootwrap designate- sink designate- status designate- worker python3/ dist-packages/ designate/ backend/ impl_bind9. py python3/ dist-packages/ designate/ tests/unit/ backend/ test_bind9. py
ubuntu@
/usr/bin
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/bin/
/usr/lib/
/usr/lib/