Comment 4 for bug 1312217

I cannot reproduce this bug after testing many combinations.

This issue may have been resolved by other changes elsewhere. After
assuring myself that the first and second combination work on my
own computer with the formerly broken account. I switched to a new
account to find the combination that breaks. I found None. I am
running CI in canonistack with 1.18.2 admin-secret + control-bucket
because I don't trust Juju without the options.

Juju version and config options localhost canonistack-slave
1.18.2 admin-secret + control-bucket O O
1.18.2 admin-secret O O
1.18.2 none O O
1.19.1 admin-secret + control-bucket O O
1.19.1 admin-secret O O
1.19.1 none O O

The difference between now and a few weeks ago is the juju version.
We experienced this bug with juju 1.18.0 and early version of 1.19.0.
If this was a bug in juju it was fixed in the 1.18.1 or 1.18.2 release.

I have setup Juju ci to run hourly health checks with 1.18.2 in
canonistack. If there are no errors, I will enable 1.19.3 deploy and
upgrade tests.