Designate-agent package should not be created for 18.0.0 (Caracal/2024.1)

Bug #2065597 reported by Bartosz Woronicz
This bug affects 1 person
Affects Status Importance Assigned to Milestone
designate (Ubuntu)

Bug Description

The designate-agent binary was removed in Caracal release:

Please see the release notes here:
>Designate-agent removal is complete in this version of designate.

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
  Installed: 1:14.0.4-0ubuntu1
  Candidate: 1:18.0.0-0ubuntu1~cloud0
  Version table:
     1:18.0.0-0ubuntu1~cloud0 500
        500 jammy-updates/caracal/main amd64 Packages

This package contains auto-generated (with openstack-pkg-tools) service:
ubuntu@juju-8a251a-6-lxd-0:~$ dpkg -L designate-agent
ubuntu@juju-8a251a-6-lxd-0:~$ apt-cache policy show python3-designate
  Installed: 1:18.0.0-0ubuntu1~cloud0
  Candidate: 1:18.0.0-0ubuntu1~cloud0
  Version table:
 *** 1:18.0.0-0ubuntu1~cloud0 500
        500 jammy-updates/caracal/main amd64 Packages
        100 /var/lib/dpkg/status

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

The proposed solution would be either:
1. keep the boilerplatte package designate-charm but remove the service designate-agent
2. remove the package entirely and do not create version 18.0.0-x of designate-agent

Revision history for this message
Bartosz Woronicz (mastier1) wrote :

This is related bug report for the charm:

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.