Comment 3 for bug 1849561

Hey Ian,

I've re-run remove-offer:

$ juju remove-offer --force ud-ldap-server:udprovide -y --debug
11:35:44 INFO juju.cmd supercommand.go:57 running juju [2.6.9 gc go1.10.4]
11:35:44 DEBUG juju.cmd supercommand.go:58 args: []string{"/snap/juju/9102/bin/juju", "remove-offer", "--force", "ud-ldap-server:udprovide", "-y", "--debug"}
11:35:44 INFO juju.juju api.go:67 connecting to API addresses: [10.17.101.45:17070 10.17.101.46:17070 10.17.101.44:17070]
11:35:44 DEBUG juju.api apiclient.go:1092 successfully dialed "wss://10.17.101.45:17070/api"
11:35:44 INFO juju.api apiclient.go:624 connection established to "wss://10.17.101.45:17070/api"
11:35:44 INFO juju.juju api.go:303 API endpoints changed from [10.17.101.45:17070 10.17.101.44:17070 10.17.101.46:17070] to [10.17.101.45:17070 10.17.101.46:17070 10.17.101.44:17070]
11:35:44 DEBUG juju.api monitor.go:35 RPC connection died
11:35:44 INFO cmd supercommand.go:502 command finished

I've uploaded diagnostics (show-status-log, sanitized bundles, log excerpts from the controller and the units): https://private-fileshare.canonical.com/~sabaini/14c66249-504d-49d1-84a4-e2f9e1ce2af0/lp1849561.tar.gz

There is only one controller. Fwiw if it helps with filtering, Juju models were upgraded to 2.6.9 on 2019-10-17

cheers,
peter.