DestroyEnvironment does not remove entry from envusers

Bug #1422791 reported by Roger Peppe
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
juju-core
Fix Released
Medium
Jesse Meek

Bug Description

In a multi-environment situation, if DestroyEnvironment is called on a
sub-environment, the relevant entry is not removed from the envusers
collection. This in turn means that EnvironmentManagerAPI.ListEnvironments fails with an
"environment not found" error, even though some environments may exist.

Revision history for this message
Curtis Hovey (sinzui) wrote :

Hi Tim. Does this issue need to be fixed for the 1.23.0 release?

Changed in juju-core:
status: New → Triaged
importance: Undecided → High
tags: added: destroy-environment users
Changed in juju-core:
importance: High → Medium
Tim Penhey (thumper)
Changed in juju-core:
assignee: nobody → Jesse Meek (waigani)
milestone: none → 1.23
Curtis Hovey (sinzui)
Changed in juju-core:
milestone: 1.23 → none
Revision history for this message
Jesse Meek (waigani) wrote :

This bug was fixed with commit 7927208136d0aa9b3a7926bbb38849bd1fbe95f1

Changed in juju-core:
status: Triaged → Fix Committed
Curtis Hovey (sinzui)
Changed in juju-core:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.