If your initial installation of OpenNMS disables Capsd in service configuration and enables Provisiond in opennms.properties to handle discovery, there are no services registered in the DB. So, if you decide to provision a node before doing any auto discovery, the drop down list of services are not populated.
I found this in snapshot (1.9.3) but probably effects current stable release, too.
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Martin Lärcher April 7, 2011 at 4:18 PM
Can confirm this also happens in current stable 1.8.10.
If we add a specific service only to one node in group we have to configure it in the foreign source? When we synchronizing the group is this service detected on the nodes we don't like to have them?
Matt Brozowski April 6, 2011 at 5:15 PM
I have changed the code so that the list of items in the service drop down now comes from the foreign source of the group rather than the database. This will allow you do define the services you want available by adding detectors to the foreign source.
If your initial installation of OpenNMS disables Capsd in service configuration and enables Provisiond in opennms.properties to handle discovery, there are no services registered in the DB. So, if you decide to provision a node before doing any auto discovery, the drop down list of services are not populated.
I found this in snapshot (1.9.3) but probably effects current stable release, too.