Comment 2 for bug 1866553

Thanks for reporting! I can't find a specific charms.reactive or charm-helpers commit that would be the fix for this, yet it seems to have been fixed meanwhile. We see in the original logs [0] that in order to reproduce this we need a bundle with barbican connected to vault over the `certificates` relation. Thus I created a bionic-stein.yaml bundle [1] and did this a few times:

juju deploy ./bionic-stein.yaml
juju remove-application --force barbican

Each time in my case the vault unit managed to run the certificates-relation-departed and certificates-relation-joined with no issues. Also the `--force` flag shouldn't have any impact on the errors of applications not being removed. For the record I'm using Juju 2.8.7.

Closing this bug for now. Don't hesitate to re-open if you still encounter this and please provide more information (e.g. charm versions and bundle). Thanks!

[0] https://pastebin.canonical.com/p/4b4rdNmZYR/
[1] https://paste.ubuntu.com/p/nrsrSnQrMw/