With the latest version of the etcd charm (revision 411) I see the following error in the logs:
unit-etcd-1: 09:24:00 INFO unit.etcd/1.juju-log Invoking reactive handler: reactive/etcd.py:439:set_snapd_timer
unit-etcd-1: 09:24:00 INFO unit.etcd/1.juju-log setting snapd_refresh timer to: None
unit-etcd-1: 09:24:00 INFO unit.etcd/1.juju-log Set config refresh.timer=None for snap core
unit-etcd-1: 09:24:00 DEBUG unit.etcd/1.update-status error: cannot perform the following tasks:
unit-etcd-1: 09:24:00 DEBUG unit.etcd/1.update-status - Run configure hook of "core" snap (run hook "configure": cannot parse "None": "None" is not a valid weekday)
unit-etcd-1: 09:24:00 ERROR unit.etcd/1.juju-log Hook error:
Traceback (most recent call last):
File "/var/lib/juju/agents/unit-etcd-1/.venv/lib/python3.6/site-packages/charms/reactive/__init__.py", line 73, in main
bus.dispatch(restricted=restricted_mode)
File "/var/lib/juju/agents/unit-etcd-1/.venv/lib/python3.6/site-packages/charms/reactive/bus.py", line 390, in dispatch
_invoke(other_handlers)
File "/var/lib/juju/agents/unit-etcd-1/.venv/lib/python3.6/site-packages/charms/reactive/bus.py", line 359, in _invoke
handler.invoke()
File "/var/lib/juju/agents/unit-etcd-1/.venv/lib/python3.6/site-packages/charms/reactive/bus.py", line 181, in invoke
self._action(*args)
File "/var/lib/juju/agents/unit-etcd-1/charm/reactive/etcd.py", line 451, in set_snapd_timer
snap.set_refresh_timer(timer)
File "lib/charms/layer/snap.py", line 231, in set_refresh_timer
set(snapname='core', key='refresh.timer', value=timer)
File "lib/charms/layer/snap.py", line 197, in set
['snap', 'set', snapname, '{}={}'.format(key, value)])
File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['snap', 'set', 'core', 'refresh.timer=None']' returned non-zero exit status 1.
This is with having three instances of etcd running.
Simon, I'm running CDK with etcd-411 and don't have this issue, so there must be something unique to your deployment that's causing this. Can you include `juju status` output please, or a copy of the bundle you deployed, including any configuration that's been set on the charms? Thanks!