Environment.Users does not take into consideration the current environment
Bug #1465873 reported by
Tim Penhey
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
juju-core |
Fix Released
|
Medium
|
Jesse Meek |
Bug Description
Environment.Users relies on the current state environment being the same environment as the one we are asking for the users from.
If we are in one environment, and ask for an Environment for a different envUUID, we get a valid Environment object backed by a state connection that will filter by a different environment uuid.
The Users method needs to check the envUUID of the state connection and create one forEnviron if necessary.
Changed in juju-core: | |
importance: | High → Medium |
Changed in juju-core: | |
status: | Triaged → Fix Released |
milestone: | none → 1.26-alpha1 |
To post a comment you must log in.
Damn... not as easy as all that as the EnvUser objects passed back will then be backed by a closed state.
Might be better to remove this method all together.