Disable services until initial render of configuration
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Base Layer |
Fix Released
|
Medium
|
Frode Nordahl | ||
charms.openstack |
Fix Released
|
Medium
|
Frode Nordahl |
Bug Description
Most of the software installed and managed by charms will not operate correctly until required charm relations have been established and configuration is rendered.
However, the packages installed by the charm often enable the service by default and the init system will make repeated attempts to start the service until it finally gives up.
This may leave units in a non-functional state since when the charm finally renders the config and attempts to (re-)start the service, the init system may have marked it as failed and refusing to start it.
The situation described above also leads to a lot unnecessary noise in the system logs.
A pattern has emerged in our reactive charms where the charm author explicitly mask services, prohibiting the init system from attempting to start them, until initial render of configuration has happened.
We should implement opt-in default handlers for this pattern in `layer-openstack` and `charms.openstack`.
Changed in layer-openstack: | |
status: | New → In Progress |
Changed in charms.openstack: | |
status: | New → In Progress |
Changed in layer-openstack: | |
importance: | Undecided → Medium |
Changed in charms.openstack: | |
importance: | Undecided → Medium |
Changed in layer-openstack: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in charms.openstack: | |
assignee: | nobody → Frode Nordahl (fnordahl) |
Changed in layer-openstack: | |
status: | In Progress → Fix Released |
Fix proposed to branch: master /review. opendev. org/696464
Review: https:/