Charm blocked on designate services with Runtime directory is not valid reported in syslog
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Designate Charm |
Fix Released
|
Medium
|
James Page | ||
OpenStack Glance Charm |
Incomplete
|
Undecided
|
Unassigned | ||
designate (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
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-
Syslog on the unit has the following:
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
Jul 19 07:47:58 juju-f3de6a-3-lxd-2 systemd[1]: [/lib/systemd/
The crashdump is the same as what's attached to bug 1782640.
Version details and artifacts are here: https:/
description: | updated |
Changed in charm-designate: | |
milestone: | none → 18.08 |
Changed in charm-designate: | |
status: | Fix Committed → Fix Released |
Note that this is with the master branch charms - stable charms are just fine.