Comment 2 for bug 2047584

Debugging the hooks manually, it seems that i have to trip `/var/lib/juju/agents/unit-ceph-osd-*/charm/hooks/config-changed` in order for it to pick up the updated OSD...
Wondering if this has anything to do with the v3 semantic changes around `juju run ...`

In any case, seems units dont pick up on config changes so they dont run pending actions.
The status update refreshed OSD states, and it correctly reports everything about prior state, but does not try to find the new disk:
```
unit-ceph-osd-9: 01:21:17 DEBUG unit.ceph-osd/9.juju-log got journal devs: set()
unit-ceph-osd-9: 01:21:17 INFO unit.ceph-osd/9.juju-log Skipping osd devices previously processed by this unit: ...
unit-ceph-osd-9: 01:21:17 DEBUG unit.ceph-osd/9.juju-log Checking for pristine devices: "[]"
unit-ceph-osd-9: 01:21:17 INFO unit.ceph-osd/9.juju-log ceph bootstrapped, rescanning disks
unit-ceph-osd-9: 01:21:17 INFO unit.ceph-osd/9.juju-log Making dir /var/lib/charm/ceph-osd ceph:ceph 555

```