[2.9.16 & 2.9.17] juju trust gets lost if juju config is run on application
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Fix Released
|
High
|
Harry Pidcock |
Bug Description
We are seeing instances of juju trust calls getting lost when called right after deploying a bundle.
The bundle deploy happens as normal, juju trust is called, but then the application (openstack-
If it matters, we're doing this programmatically, so there is almost no delay between juju deploy finishing, and juju trust getting called.
Additionally, we have only started seeing this error in the last 24 hours.
I'm working on collecting logs from a 2.9.17 run that is exhibiting this problem, and will add them as soon as they are available.
from the crashdump, you should be able to see the current status of the openstack-
In the foundation log, if you look for `juju trust` you can see trust was called just before juju wait was called, and after the deploy has finished
foundation.log:
https:/
full test run:
https:/
Changed in juju: | |
status: | Triaged → In Progress |
assignee: | nobody → Harry Pidcock (hpidcock) |
Changed in juju: | |
milestone: | 2.9.18 → 2.9.19 |
Changed in juju: | |
status: | In Progress → Fix Committed |
Changed in juju: | |
status: | Fix Committed → Fix Released |
It's probably worth mentioning:
I havent been able to reproduce this on aws, where we run `juju trust` in the same way