OpenNMS has multiple optional features installed via Karaf that require configuration to work.
Usually, and because I always use automation tools to configure the solutions for customers and when building test environments, it is an unattended script responsible for configuring everything.
All the features I tried in the past can be configured this way, and never had issues with them.
Unfortunately, that is not the case with Situations Feedback. After a clean installation (i.e., nothing inside /opt/opennms/data), the feature tries to start but it doesn't seem to work, and I can see the following on the Karaf shell:
This Situations Feedback plugin is configured very similarly to the Elasticsearch forwarders for Events and Alarm History. These two always work when setting them automatically (never had issues with them or any other feature), but I haven't found a way to start the Situations Feedback in a similar way that always works.
The following is the easiest fix I found that always works for me:
The above script reconfigures the feature. Internally, that triggers the reload of all the dependent bundles, and after that, the plugin works as intended. Most of the time, after doing this, the feature survives an OpenNMS restart. But, if the user removes the content of the data directory prior to starting OpenNMS (like on an upgrade), the above script must be executed one more time to fix the problem.