With juju 1.24 this bug appears to be hit on state servers started with 'juju ensure-availability' during cloud-init upgrade, unless enable-os-refresh-update and enable-os-upgrade are set to false.
With juju 1.24 this bug appears to be hit on state servers started with 'juju ensure- availability' during cloud-init upgrade, unless enable- os-refresh- update and enable-os-upgrade are set to false.