| 2015-05-15 10:45:54 |
Kirill Zaitsev |
description |
To reproduce:
* Upload a package
* Deploy it in an environment
* Delete the package
* Try to delete the environment
Deletion fails because the engine tries to load the package. In this circumstance I don't think it makes sense to fail; if the package is gone, we can't do any cleanup because we don't know what to do, but we should still allow the environment to be deleted i think.
Some things that could also mitigate this:
* issue a warning when deleting in-use packages
* disallow deletion for in-use packages (this is probably not what we want, especially for public ones)
* as a last ditch resort, delete the heat stack (maybe add a 'force' flag to indicate that potentially there are things that won't get cleaned up) |
To reproduce:
* Upload a package
* Deploy it in an environment
* Delete the package
* Try to delete the environment
Deletion fails because the engine tries to load the package. In this circumstance I don't think it makes sense to fail; if the package is gone, we can't do any cleanup because we don't know what to do, but we should still allow the environment to be deleted i think.
Some things that could also mitigate this:
* issue a warning when deleting in-use packages
* disallow deletion for in-use packages (this is probably not what we want, especially for public ones)
* as a last ditch resort, delete the heat stack (maybe add a 'force' flag to indicate that potentially there are things that won't get cleaned up)
Related blueprint: https://blueprints.launchpad.net/murano/+spec/murano-package-tombstones |
|
| 2015-05-19 14:24:08 |
Kirill Zaitsev |
description |
To reproduce:
* Upload a package
* Deploy it in an environment
* Delete the package
* Try to delete the environment
Deletion fails because the engine tries to load the package. In this circumstance I don't think it makes sense to fail; if the package is gone, we can't do any cleanup because we don't know what to do, but we should still allow the environment to be deleted i think.
Some things that could also mitigate this:
* issue a warning when deleting in-use packages
* disallow deletion for in-use packages (this is probably not what we want, especially for public ones)
* as a last ditch resort, delete the heat stack (maybe add a 'force' flag to indicate that potentially there are things that won't get cleaned up)
Related blueprint: https://blueprints.launchpad.net/murano/+spec/murano-package-tombstones |
NOTE: Current behaviuor of the bug changed. An error still occurs, but the env is deleted (without deleteing the stack or calling any destroy() methods)
To reproduce:
* Upload a package
* Deploy it in an environment
* Delete the package
* Try to delete the environment
Deletion fails because the engine tries to load the package. In this circumstance I don't think it makes sense to fail; if the package is gone, we can't do any cleanup because we don't know what to do, but we should still allow the environment to be deleted i think.
Some things that could also mitigate this:
* issue a warning when deleting in-use packages
* disallow deletion for in-use packages (this is probably not what we want, especially for public ones)
* as a last ditch resort, delete the heat stack (maybe add a 'force' flag to indicate that potentially there are things that won't get cleaned up)
Related blueprint: https://blueprints.launchpad.net/murano/+spec/murano-package-tombstones |
|
