Public bug reported: As the title says, in case fullstack_fixtures.EnvironmentFixture fails to start because 'wait_until_env_is_up' didn't return successfully (for example, there was a problem with one of the agents), cleanUp isn't called. This causes all the resources of the fixtures that are used in the environment (processes, configurations, namespaces...) not to be cleaned.
** Affects: neutron Importance: Undecided Assignee: John Schwarz (jschwarz) Status: New ** Changed in: neutron Assignee: (unassigned) => John Schwarz (jschwarz) -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1453888 Title: Fullstack doesn't clean resources if environment fails to start Status in OpenStack Neutron (virtual network service): New Bug description: As the title says, in case fullstack_fixtures.EnvironmentFixture fails to start because 'wait_until_env_is_up' didn't return successfully (for example, there was a problem with one of the agents), cleanUp isn't called. This causes all the resources of the fixtures that are used in the environment (processes, configurations, namespaces...) not to be cleaned. To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1453888/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp