MuranoPlException: [yaql.language.exceptions.NoMatchingMethodException]: in engine logs after removing environment that was redeployed
Bug #1503715 reported by
Anastasia Kuznetsova
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Murano |
Fix Released
|
High
|
Stan Lagun | ||
Liberty |
Fix Released
|
High
|
Stan Lagun | ||
Mitaka |
Fix Released
|
High
|
Stan Lagun |
Bug Description
Steps to reproduce:
1. Create Murano environment
2. Add application to the env
3. Deploy it
4. After successful deployment, remove added component from env
5. Redeploy environment
6. Add two apps to the env
7. Redeploy environment
8. After successful redeploy, remove environment
9. Take a look at murano-engine log
Observed result:
Murano environment was successfully deleted, heat stack was deleted too.
But there is a huge TRACE in the murano-engine.log
http://
Expected result:
No traces in logs.
Changed in murano: | |
status: | New → Triaged |
importance: | Undecided → Medium |
importance: | Medium → Low |
milestone: | none → mitaka-1 |
Changed in murano: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Faced this one while testing new k8s api.
In case with k8s this bug cause environment hanging in 'DELETING' state.
All stacks were deleted, but environment - not.
Regarding this, raising importance to high.