Downtime on a removed object are never closed.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 76
- Forks
- 23
- Avg merge
- 13h 37m
- Merged PRs (30d)
- 11
Description
Describe the bug
If a object with a Downtime gets disabled (even just temporary) the end of the associated Downtime is never written out to the IDO / IcingaDB.
To Reproduce
- Create a host in the director and deploy it.
- Create a downtime on the host
- Use the director to roll back to an older version
4.Redeploy the new version
Expected behavior
I would expect the Downtime to be terminated once the object is deactivated (The actual_end_time set to the current time). But since the downtime is dropped without ever setting this field, the object looks in the reports as if it where in a constant downtime. which does not correspond to the internal state of icinga2.
Screenshots
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the host rollback and redeploy sequence described in the issue, then trace how a disabled object’s downtime is persisted to the IDO/IcingaDB. Done means the downtime receives an actual_end_time when the object is deactivated and reports no longer show it as continuous.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100