influxdata / influxdata/kapacitor

Deleted tasks are still enabled and can't be disabled or deleted

Open
#1,069 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
2.4k
Forks
479
Avg merge
4d 16h
Merged PRs (30d)
4

Description

Kapacitor 1.1.0 (git: master 939fdf670b028c142944977dcfcb045cac2343ed)
Ubuntu 14.04.5 LTS

When I define a kapacitor task like:

```
kapacitor define healthcheck_alert ...
```

and then delete it like:

```
kapacitor delete tasks healthcheck_alert
```

the task seems to become a 'zombie'. It is not shown when running `kapacitor list tasks`, but running `kapacitor show healthcheck_alert` shows:

```
ID: healthcheck_alert
Error:
Template:
Type: batch
Status: enabled
Executing: true
Created: 29 Nov 16 18:01 UTC
Modified: 29 Nov 16 20:36 UTC
LastEnabled: 29 Nov 16 20:36 UTC
Databases Retention Policies: ["service_status"."autogen"]
...
```

I now can't seem to delete, define, enable or disable this task. These kapacitor commands run without error but the task remains in exactly the same state. It can't be updated, deleted or disabled and is still sending alerts. I've tried to disable and delete this task, but `kapacitor show` still shows it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the sequence with `kapacitor define`, `kapacitor delete tasks`, and `kapacitor show`, then compare the behavior of `list`, `enable`, and `disable`. Trace the task lifecycle behind these command entry points and verify that deleting a task removes it from `show` and stops its alerts. There are no files or tests named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, cli, observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.