-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 1.8.7, 1.8.9
-
Fix Version/s: 1.9.92
-
Component/s: Provisioning / Discovery / Importer
-
Security Level: Default (Default Security Scheme)
-
Labels:
-
Environment:Version: 1.8.7
Server Time: Tue Feb 15 10:37:14 GMT 2011
Client Time: Tue Feb 15 2011 10:37:14 GMT+0000 (IST)
Java Version: 1.5.0_18 Sun Microsystems Inc.
Java Virtual Machine: 1.5.0_18-b02 Sun Microsystems Inc.
Operating System: Linux 2.6.34-12-desktop (amd64)
Servlet Container: jetty/6.1.24 (Servlet Spec 2.5)
User Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12Version: 1.8.7 Server Time: Tue Feb 15 10:37:14 GMT 2011 Client Time: Tue Feb 15 2011 10:37:14 GMT+0000 (IST) Java Version: 1.5.0_18 Sun Microsystems Inc. Java Virtual Machine: 1.5.0_18-b02 Sun Microsystems Inc. Operating System: Linux 2.6.34-12-desktop (amd64) Servlet Container: jetty/6.1.24 (Servlet Spec 2.5) User Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-GB; rv:1.9.2.12) Gecko/20101026 SUSE/3.6.12-0.7.1 Firefox/3.6.12
Using Provisioning Groups, I wished to auto-add nodes into surveillance categories. While they are added to the correct categories on an initial synchronization, they are subsequently removed from those surveillance categories on any additional manual synchronization.
Sequence:
Set NodeCategorySettingPolicys in a Provison Group. Initially 4 polices based on sysoid to add nodes to 4 surveillance categories.
Manually add a number of nodes to the Provision Group.
Run Synchronization.
Results are as expected, nodes get added into 4 surveillance categories.
Manually add more nodes to Provision Group.
Run Synchronization.
Newly added nodes are added to 4 surveillance categories. Previously added nodes are removed from surveillance categories.
Alternatives tried:
Removed all nodes.
Manually added nodes to to the Provision Group.
Run Synchronization.
Results are as expected, nodes get added into 4 surveillance categories.
Run Synchronization again.
Previously added nodes are removed from surveillance categories.
Removed all nodes.
Set NodeCategorySettingPolicys in a Provison Group using foreignSource as a key instead. 4 policies are created.
Manually add a number of nodes to the Provision Group.
Run Synchronization.
Results are as expected, nodes get added into 4 surveillance categories.
Manually add more nodes to Provision Group.
Run Synchronization.
Newly added nodes are added to 4 surveillance categories. Previously added nodes are removed from surveillance categories.
Removed all nodes.
Configured only one NodeCategorySettingPolicy in the Provision Group, using foreignSource as a key.
Manually add a node to the Provision Group.
Run Synchronization.
Results are as expected, node gets added to one surveillance category
Manually add another node to the Provision Group
Run Synchronization.
New added node is added to the surveillance category, previous added node is removed from surveillance category.
I have the capsd service disabled. I also had org.opennms.provisiond.enableDiscovery=true in opennms.properties, and then tried the same test with it set to false, with the same issue reoccurring.
This would be a problem for manually added nodes when you are using Surveillance Categories for filters on Polling, Data Collection, Notifications etc.
I can't identify any output from the provisiod.log that differentiates between categorization for nodes that initially get categorized and those previous nodes that are getting un-categorized.
I've added the provisiond.log in DEBUG mode, last entries are the most recent testing.
Regards
Patrick
- is duplicated by
-
-
- Resolved
-
