ack-sel is not very granular

Bug #1928403 reported by Andrea Ieri
22
This bug affects 4 people
Affects Status Importance Assigned to Milestone
hw-health-charm
Fix Released
Wishlist
Mert Kirpici

Bug Description

In bug 1901735 we implemented the ack-sel action by relying on the --date-range ipmi-sel option. This option does not accept anything more granular than whole days, and as a consequence it is not possible to silence an alert produced by a SEL entry that is less than a day old.
It would be useful to find a workaround, as operators are currently forced to downtime alerts for at least one day before they are able to silence them via this action.

Tags: bseng-469

Related branches

Edin S (exsdev)
Changed in charm-hw-health:
importance: Undecided → Wishlist
Revision history for this message
Joe Guo (guoqiao) wrote :

If today is Jan 05 2022, ack-sel will render this in cron job:

--seloptions --date-range=01/05/2022-now

However, this will still include the events occurred on 2022-01-05, and fail to mute current alert.

A few ways to workaround:

1) use 01/06/2022 as start date.
2) use `--exclude-date-range=01/01/1970-01/05/2022` instead
3) get the last event id, e.g.: 42, and use `--exclude-display-range=0-42` instead.

for 1) and 2), it will have side effect to also ignore following alerts in the same day.
3) seems to be accurate, but, it looks like, when we clear sel, the id will go back to 0. So new generated alerts 0-42 may be ignored unexpected. Need to confirm this.

Andrea Ieri (aieri)
tags: added: bseng-469
Changed in charm-hw-health:
status: New → In Progress
assignee: nobody → Mert Kirpici (mertkirpici)
Changed in charm-hw-health:
status: In Progress → Fix Committed
Changed in charm-hw-health:
milestone: none → 23.01
Changed in charm-hw-health:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.