Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.8.3
-
Fix Version/s: 1.9.92
-
Component/s: Web UI - General
-
Security Level: Default (Default Security Scheme)
-
Labels:None
-
Environment:Operating System: Linux
Platform: PC
-
Bugzilla Id:4085
Description
Tested with 1.8.3
How to reproduce:
1. provision a node
<node node-label="telnet test node" foreign-id="telnet test node foreign id">
<interface status="1" snmp-primary="N" ip-addr="111.111.111.111" descr="">
<monitored-service service-name="Telnet"/>
<monitored-service service-name="ICMP"/>
</interface>
</node>
2. import the provisioning group
3. look at the node page in the webui
icmp will be down (unless the IP is available), telnet will be not monitored (at least in the standard configuration).
4. add another interface to the node
<node node-label="telnet test node" foreign-id="telnet test node foreign id">
<interface status="1" snmp-primary="N" ip-addr="111.111.111.111" descr="">
<monitored-service service-name="Telnet"/>
<monitored-service service-name="ICMP"/>
</interface>
<interface status="1" snmp-primary="N" ip-addr="222.222.222.222" descr="">
<monitored-service service-name="Telnet"/>
<monitored-service service-name="ICMP"/>
</interface>
</node>
5. import the provisioning group
6. look at the node page in the webui
Telnet on the first interface will be shown as being available 100%
Telnet on the second interface will be shown as not monitored
7. restart OpenNMS
8. look at the node page in the webui
Both Telnet services will be shown as not monitored
This can be highly confusing.