aodh-api service fails to start on xenial newton with SSL

Bug #1850767 reported by Liam Young on 2019-10-31
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack AODH Charm
Liam Young

Bug Description

When deploying aodh using the charms ssl-* params (as opposed to vault) the aodh-api service fails to start and the charm exposes this via workload status:

App Version Status Scale Charm Store Rev OS Notes
aodh 3.0.4 blocked 1 aodh jujucharms 98 ubuntu

Unit Workload Agent Machine Public address Ports Message
aodh/0* blocked idle 1 8042/tcp Services not running that should be: aodh-api

Liam Young (gnuoy) on 2019-10-31
Changed in charm-aodh:
status: New → Confirmed
importance: Undecided → Medium
assignee: nobody → Liam Young (gnuoy)
milestone: none → 20.01

Fix proposed to branch: master

Changed in charm-aodh:
status: Confirmed → In Progress

Submitter: Zuul
Branch: master

commit 5050885df955b9882fb0c249bb08688798a9f177
Author: Liam Young <email address hidden>
Date: Thu Oct 31 13:17:33 2019 +0000

    Do not rely on when_file_change for systemd reload

    Systemd was not relying being reloaded when the definition
    file for aodh-api changed. The reload was supposed to be
    triggered by the when_file_changed decorator. However,
    there are a number of issues with when_file_changed decorator (*1,
    *2, *3) and the decorator has now been deprecated *4.

    This change ensures the reload happens without relying on
    the decorator.


    Closes-Bug: #1850767

    Change-Id: I7c528a53a4de8a4a85bf655fc242b0f38fd0754b

Changed in charm-aodh:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.