Comment 22 for bug 1333162

We're seeing this again on 1.25.12 I believe.

We have a Jenkins instance that runs about 80 jobs each weekend, a mix of Juju 1.25.12 and 2.2.2. This is running against the OpenStack provider, and each job spins up a Juju environment and then runs tests. For the last few weekends we've had a large number of failures in jobs, all with the same error as per the original description.

Looking at one example this morning I saw the following message:

"Multiple security_group matches found for name 'juju-mojo-ols-logging-trusty', use an ID to be more specific."

I confirmed manually that there were no security groups matching that name, and reran the job. It was able to bootstrap without problems. The first part of the job does:

juju destroy-environment --force -y $JUJU_ENV

It then runs juju status in a loop until the output matches:

'Please check your credentials or use .* to create a new environment.'

It then runs juju bootstrap.