** Changed in: charm-designate
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925233
Title:
[bionic-ussuri] designate-mdns.service: Failed with result 's
Seen again in:
https://solutions.qa.canonical.com/testruns/testRun/fb6f362f-eba9-41f2-ae31-c89c50bb392e
Artifacts: https://oil-
jenkins.canonical.com/artifacts/fb6f362f-eba9-41f2-ae31-c89c50bb392e/index.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
here is an example on how to reuse config.rendered flag
https://github.com/openstack/charm-manila/blob/b75e6ed3ce6b2c061105ac8226a778e1ec3685d4/src/reactive/manila_handlers.py#L178
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
We discussed this issue with the team and the agreement is that the
charm should disable/mask the service until the configuration has been
rendered, this is a pattern already used in other charms. For the
reactive charms there is a handler for this -
https://github.com/openstack/charm-layer-
openst