Comment 2 for bug 1592872

I haven't been able to reproduce locally. I have a couple questions for you:

1 - Can you reproduce this problem reliably?

2 - Is there a particular bundle you're using when you run into this?

3 - When you see it again, can you also include the full `juju status` and `juju status --format=yaml` output?