Michael Wu created EAGLE-308:
--------------------------------
Summary: Consistency issue: deleting a topology doesn't delete
existing topology-execution bound to it.
Key: EAGLE-308
URL: https://issues.apache.org/jira/browse/EAGLE-308
Project: Eagle
Issue Type: Bug
Affects Versions: v0.3.0
Reporter: Michael Wu
Assignee: Zhao, Qingwen
Fix For: v0.4.0
Reproduce:
1. create a topology named "demo001", and create one topology-execution bound
to "demo001".
2. on "management" page, delete "demo001", and confirm the deletion in the
pop-up overlay (as a result the topology should be deleted as expected).
3. then turn to "monitoring" page, the topology-execution bound to "demo001"
still exists on the page.
Point of view: this behavior seems violating the consistency of binding a
topology to an execution.
Action required: please verify and confirm if this is a bug that the execution
should be deleted together with the deletion of "demo001"; or otherwise, in the
pop-up overlay of topology deletion, there should be a notification for
customers to know that after deleting a topology, corresponding execution will
be in wrong status and they should be deleted manually.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
