Unable to manually provision service via GUI without first defining detector
Description
Environment
System Details
--------------
OpenNMS Version: 1.10.0
Java Version: 1.6.0_30 Sun Microsystems Inc.
Java Virtual Machine: 20.5-b03 Sun Microsystems Inc.
Operating System: Linux 2.6.18-274.12.1.el5 amd64
Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_3) AppleWebKit/535.11 (KHTML, like Gecko) Chrome/17.0.963.46 Safari/535.11
Acceptance / Success Criteria
None
Lucidchart Diagrams
Activity
Show:

Benjamin Reed March 26, 2012 at 12:38 PM
fixed in 1.10 and master

Benjamin Reed March 14, 2012 at 10:16 AM
We discussed this in scrum, the easy fix is to make the list be populated with any service known in the database+capsd+requisition.
Fixed
Details
Details
Assignee

Reporter

Labels
Components
Fix versions
Affects versions
Priority
PagerDuty
PagerDuty Incident
PagerDuty

PagerDuty Incident
Created February 13, 2012 at 10:17 AM
Updated January 27, 2017 at 4:20 PM
Resolved March 26, 2012 at 12:38 PM
I have been testing out the new 1.10 and one thing I noticed is that if I do not have a detector for the service created under the foreign source I cannot assign the service to the node within the provisioning group because services other than the defined detector are not available. In 1.8, I show all the pollers defined as services to assign not just the one configured as a detector. If I add the detector for the service I want to add to the node then I can add it. In 1.8 and previous I have used this to set the foreign source to discover only the ICMP service for new router interfaces and anything else I would add under the node manually. One of the reasons I want to do this very granular provisioning (for services other than ICMP) is because of services like SSH where I want to add this to servers but not on routers where they could be potentially 100's of SSH services discovered.
A few work arounds:
Add service to node via provision.pl
Add the appropriate detector to the foreign source then add the service to the provisioning requisition node then remove the detector once added
I see the same result with capsd enabled or disabled.
-Eric