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

cmd/icingadb-migrate: ignore icinga_downtimehistory#was_started=0 rows #623

Merged
merged 1 commit into from
Jul 28, 2023

Conversation

Al2Klimov
Copy link
Member

Such appear e.g. for scheduled but never triggered flexible Downtimes. Not triggered = no events.

In addition this

fixes #621

for reasons Julian described in #622 (review). (I tested that.)

@Al2Klimov Al2Klimov added the bug Something isn't working label Jul 27, 2023
@Al2Klimov Al2Klimov added this to the 1.1.1 milestone Jul 27, 2023
@cla-bot cla-bot bot added the cla/signed label Jul 27, 2023
@julianbrost
Copy link
Contributor

Did you test whether this PR still writes any downtime history? I'm missing a change in cmd/icingadb-migrate/embed/downtime_query.sql and I suspect without that, WasStarted will always have the default zero value.

Such appear e.g. for scheduled but never triggered flexible Downtimes.
Not triggered = no events.
@julianbrost julianbrost merged commit b05128e into master Jul 28, 2023
31 checks passed
@julianbrost julianbrost deleted the was_started-621 branch July 28, 2023 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cla/signed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Migration: constraint violation in sla_history_downtime.downtime_end
2 participants