Charm blocked on designate services with Runtime directory is not valid reported in syslog

[John George]

Foundation cloud build deployment reports:
designate/0 blocked idle 3/lxd/2 10.244.41.3 9001/tcp Services not running that should be: designate-mdns, designate-zone-manager, designate-agent, designate-pool-manager, designate-central, designate-sink, designate-api

Syslog on the unit has the following:
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-mdns.service:12] Runtime directory is not valid, ignoring assignment: designate lock/designate
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-mdns.service:13] Unknown lvalue 'CacheDirectory' in section 'Service'
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-central.service:12] Runtime directory is not valid, ignoring assignment: designate lock/designate
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-central.service:13] Unknown lvalue 'CacheDirectory' in section 'Service'
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-api.service:12] Runtime directory is not valid, ignoring assignment: designate lock/designate
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-api.service:13] Unknown lvalue 'CacheDirectory' in section 'Service'
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-agent.service:12] Runtime directory is not valid, ignoring assignment: designate lock/designate
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/system/designate-agent.service:13] Unknown lvalue 'CacheDirectory' in section 'Service'

The crashdump is the same as what's attached to bug 1782640.
Version details and artifacts are here: https://solutions.qa.canonical.com/#/qa/testRun/a1d6eafb-298e-48d3-a70f-c79792a77cac

[James Page (james-page)]

Note that this is with the master branch charms - stable charms are just fine.

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/584391
Committed: https://git.openstack.org/cgit/openstack/charm-designate/commit/?id=25aa3d1b5a3047d7908590369cb5e0c8f2dd0cb5
Submitter: Zuul
Branch: master

commit 25aa3d1b5a3047d7908590369cb5e0c8f2dd0cb5
Author: James Page <email address hidden>
Date: Fri Jul 20 10:17:03 2018 -0400

    Fix group read permissions

    Recent changes in charms.openstack write configuration files
    with perms 0640; however without a group attribute on the
    client charm class, these will root.root owned.

    Ensure that config files are written using root.designate for
    this charm.

    Change-Id: I5e680e7546ad66f087c1c15cd2db60428d50afb9
    Closes-Bug: 1782644

[Seyeong Kim (seyeongkim)]

Hello, the customer faced the similar issue.

Could you please check below log as well?

It is glance node.

https://pastebin.canonical.com/p/VyVVvv3hJS/

[Sahid Orentino (sahid-ferdjaoui)]

Looks like a valid issue even if I'm not able yet to find where do we handle privileges in charmhelper, can you indicate the version used?

[Seyeong Kim (seyeongkim)]

@sahid

it is xenial-queens, charm version is below
glance charm version is 271

I'm going to check differences between 271 and latest one.
but Could you please advice me if there is some related patch between them?

Thanks.

[Seyeong Kim (seyeongkim)]

@sahid

I also found the same logs as below issue

https://github.com/lxc/lxd/issues/2004

https://pastebin.canonical.com/p/xcqPR6JShh/

maybe this shows some more clue

[Alex Kavanagh (ajkavanagh)]

Not sure if this is still an issue? Is this on new deployments or upgrades?