I don't think this is a package issue as the code in the jammy+ dnspython packages includes the collections.abc fix. Also note the subtle difference in the traceback:
There is a pip installed package on the unit as well as an apt installed package and the pip-installed version is getting picked up which causes the issue:
ubuntu@juju-c42f04-zaza-e3abc6e946c3-6:/var/lib/juju/agents/unit-neutron-api-0/charm$ pip freeze|grep -i dns
dnspython==1.16.0
I don't think this is a package issue as the code in the jammy+ dnspython packages includes the collections.abc fix. Also note the subtle difference in the traceback:
usr/local/ lib/python3. 10/dist- packages/ dns/namedict. py
There is a pip installed package on the unit as well as an apt installed package and the pip-installed version is getting picked up which causes the issue:
ubuntu@ juju-c42f04- zaza-e3abc6e946 c3-6:/var/ lib/juju/ agents/ unit-neutron- api-0/charm$ pip freeze|grep -i dns
dnspython==1.16.0
ubuntu@ juju-c42f04- zaza-e3abc6e946 c3-6:/var/ lib/juju/ agents/ unit-neutron- api-0/charm$ apt policy python3-dnspython nova.clouds. archive. ubuntu. com/ubuntu jammy/main amd64 Packages
python3-dnspython:
Installed: 2.1.0-1ubuntu1
Candidate: 2.1.0-1ubuntu1
Version table:
*** 2.1.0-1ubuntu1 500
500 http://
Running the neutron-db-manage command is successful after 'pip uninstall dnspython'.