Comment 7 for bug 2071939

I built a ceilometer Rock from Noble Proposed and was able to confirm this fixes the issue.

Built the rock by applying the following diff to https://github.com/canonical/ubuntu-openstack-rocks/blob/6707266619e67abe4e1a48ab0fe91e81b6aa5b36/rocks/ceilometer-consolidated/rockcraft.yaml#L13

diff --git a/rocks/ceilometer-consolidated/rockcraft.yaml b/rocks/ceilometer-consolidated/rockcraft.yaml
index e9679b1..6f539bf 100644
--- a/rocks/ceilometer-consolidated/rockcraft.yaml
+++ b/rocks/ceilometer-consolidated/rockcraft.yaml
@@ -5,14 +5,16 @@ description: |
   Ubuntu distribution of OpenStack ceilometer-consolidated
 version: '2024.1'

-# renovate: base: ubuntu:22.04@sha256:1b8d8ff4777f36f19bfe73ee4df61e3a0b789caeff29caa019539ec7c9a57f95
-base: ubuntu@22.04
+base: ubuntu@24.04
 platforms:
   amd64:

 package-repositories:
   - type: apt
- cloud: caracal
+ url: http://archive.ubuntu.com/ubuntu/
+ suites: [noble-proposed]
+ components: [main, universe, restricted, multiverse]
+ key-id: F6ECB3762474EDA9D21B7022871920D1991BC93C
     priority: always

 parts:

From inside the Rock
apt policy ceilometer-agent-notification
ceilometer-agent-notification:
  Installed: 2:22.0.0-0ubuntu1.1
  Candidate: 2:22.0.0-0ubuntu1.1
  Version table:
 *** 2:22.0.0-0ubuntu1.1 100
        100 /var/lib/dpkg/status

I can confirm the notification agent is now starting with the following logs:

2024-07-15 18:05:50
2024-07-15 16:05:45.757 22 INFO ceilometer.publisher.messaging [-] Publishing policy set to default

2024-07-15 18:05:49
2024-07-15 16:05:45.757 22 INFO ceilometer.publisher.messaging [-] Publishing policy set to default

Before the fix, the notification didn't start, failing on the reported exception.