I am seeing this regularly while testing deploys using a development version of conjure-up to deploy openstack services onto the lxd provider.
It is indeed intermittent, but not rare.
Some details that might help reproduce:
Because of design goals for conjure-up, we do not just 'juju deploy bundle.yaml' - conjure-up uses the juju API to deploy the applications in a bundle one at a time, and so issues many individual deploy-application requests. The most common thing I do in testing is to hit the 'deploy them all immediately' button, which issues them in a tight loop.
Let me know if I can help with tracking this down.
I am seeing this regularly while testing deploys using a development version of conjure-up to deploy openstack services onto the lxd provider.
It is indeed intermittent, but not rare.
Some details that might help reproduce:
Because of design goals for conjure-up, we do not just 'juju deploy bundle.yaml' - conjure-up uses the juju API to deploy the applications in a bundle one at a time, and so issues many individual deploy-application requests. The most common thing I do in testing is to hit the 'deploy them all immediately' button, which issues them in a tight loop.
Let me know if I can help with tracking this down.