Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Retention policy] Entities are not deleted #8150

Closed
Lhorus6 opened this issue Aug 23, 2024 · 0 comments · Fixed by #8164
Closed

[Retention policy] Entities are not deleted #8150

Lhorus6 opened this issue Aug 23, 2024 · 0 comments · Fixed by #8164
Assignees
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@Lhorus6
Copy link

Lhorus6 commented Aug 23, 2024

Description

I have configured a retention rule, since two days, that matches many entities (160 reports) but the entities are never deleted.

Environment

OCTI 6.2.14

Reproducible Steps

Steps to create the smallest reproducible scenario:

  1. Create a retention rule
  2. Apply some filters that will match a small set of reports, e.g. the test I did:

image

  1. Create the rule and wait for it to execute (you can wait 24 hours if you want). You will see that nothing is ever deleted

NB: I ran the tests on "testing". I'm leaving my retention rule active if you want to go see it (named "Test deletion issue"). It was a customer who brought this problem to my attention.

Expected Output

Actual Output

Additional information

Screenshots

My rule, active for 2 days

The value "remaining" does not decrease

Screenshot 2024-08-23 100225

The reports are there and not deleted.

Screenshot 2024-08-23 100447

@Lhorus6 Lhorus6 added bug use for describing something not working as expected needs triage use to identify issue needing triage from Filigran Product team labels Aug 23, 2024
@Jipegien Jipegien added critical use to identify critical bug to fix ASAP and removed needs triage use to identify issue needing triage from Filigran Product team labels Aug 26, 2024
@Jipegien Jipegien added this to the Bugs backlog milestone Aug 26, 2024
@JeremyCloarec JeremyCloarec self-assigned this Aug 26, 2024
@CelineSebe CelineSebe self-assigned this Aug 26, 2024
@JeremyCloarec JeremyCloarec linked a pull request Aug 26, 2024 that will close this issue
5 tasks
@JeremyCloarec JeremyCloarec added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 27, 2024
@Jipegien Jipegien added the regression Label to identify the bug as a regression of previously working feature label Aug 27, 2024
labo-flg pushed a commit that referenced this issue Aug 28, 2024
labo-flg pushed a commit that referenced this issue Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected critical use to identify critical bug to fix ASAP regression Label to identify the bug as a regression of previously working feature solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants