Details
-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 24.1.3, 25.2.1, 26.1.1
-
Fix Version/s: Meridian-2019.1.19, Meridian-2020.1.8, Meridian-2021.1.0, 28.0.0
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Sprint:Horizon 2021 - Apr 14 - Apr 28, Horizon 2021 - Apr 28 - May 12
-
HB Backlog Status:Backlog
Description
Even before ALEC was named that way (when it was OCE), I found that the bundle called ALEC :: Integrations :: OpenNMS :: Config sometimes starts correctly, and sometimes doesn't; observed on all its version, tested on pre-H24, H24, H25, and H26.
The behavior is random, and hard to reproduce consistently, which is why I think it could be a race condition.
The only workaround I found is doing the following:
admin@opennms> bundle:list | grep "ALEC.*Config"
422 │ Active │ 80 │ 1.0.2 │ ALEC :: Integrations :: OpenNMS :: Config
admin@opennms> bundle:stop 422
admin@opennms> bundle:start 422
After that, all the custom event definitions for ALEC are loaded as expected, and the advanced correlation features work as intended. Without it, some events won't have a proper definition and because of that, the correlations won't trigger.
