We're updating the issue view to help you get more done. 

Riemann not deleting monitoring when deployments are deleted

Description

We've had a report that Riemann does not delete policies when the deployments are deleted, leading to issues such as healing new nodes (when redeploying with the same deployment name as a deleted deployment) or running out of file handles (when restarting riemann with a lot of deployments).

Steps to Reproduce

Environment:
OS (CLI), HA cluster, cloud provider
------------------------------------
Manager-side, platform/HA/etc should have no effect.

Steps to reproduce:
------------------
1. Create a new deployment with healing.
2. Uninstall and delete the deployment.
3. Confirm that the deployment name still exists in /opt/riemann

Expected result:
---------------
Directory with deleted deployment's name will not exist in /opt/riemann.

Actual result:
-------------
Directory with deleted deployment's name exists in /opt/riemann.

Why Propose Close?

None

Status

Assignee

geokala

Reporter

geokala

Labels

None

Severity

Medium

Target Version

4.4

Premium Only

no

Found In Version

4.4

QA Owner

None

Bug Type

legacy bug

Customer Encountered

Yes

Customer Name

None

Release Notes

yes

Priority

None

Sprint

None

Fix versions

Priority

Unprioritized