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-
openstack/blob/master/reactive/layer_openstack.py#L161-L167
** Changed in: charm-designate
Status: Incomplete => Triaged
** Changed in: designate (Ubuntu)
Status: New => Invalid
** Changed in: charm-designate
Importance: Undecided => High
** Tags added: good-first-bug
--
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 'start-
limit-hit'
To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-designate/+bug/1925233/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
