@Seth Leger I agree, if the problem is related with Provisiond, then this is a non-UI related problem, and my comment was intended and associated only with the UI (the old one and the new one).
Seth Leger June 6, 2016 at 10:38 AM
Ah, I see now that the exception is thrown inside provisiond during the requisition import operation. The new provisioning UI probably wouldn't have fixed this. We should reconfirm that the issue still occurs but we can't mark it as fixed just because of the UI update.
Alejandro Galue June 6, 2016 at 9:14 AM
The service layer associated with the old provisioning UI is extremely different, and it uses a very different approach to handle changes on requisitions, compared with the ReST API (which is what the new UI uses). That being said, in general, nothing related with the old UI applies to the new UI, unless someone can reproduce the problem.
Seth Leger June 3, 2016 at 4:22 PM
Could this still be an issue in the new provisioning UI? Probably not I imagine.
found working in the Provisioning interface-
Test Provisioning Group created with ICMP/SNMP only detectors in foreign source, no nodes in group/DB.
Manually provision a node with valid DNS and responding services, Synchronize, node adds and shows in db, node page looks ok.
edit Requisition in Provisioning Group, trashcan created node, Synchronize. exception logs (as INFO) in provisiond.log), node is deleted.
Looks like a zero row count is unexpected by provisiond?
foreign-source:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <foreign-source date-stamp="2011-08-30T20:00:15.685-07:00" name="Test" xmlns="http://xmlns.opennms.org/xsd/config/foreign-source"> <scan-interval>1d</scan-interval> <detectors> <detector class="org.opennms.netmgt.provision.detector.icmp.IcmpDetector" name="ICMP"/> <detector class="org.opennms.netmgt.provision.detector.snmp.SnmpDetector" name="SNMP"/> </detectors> <policies> <policy class="org.opennms.netmgt.provision.persist.policies.NodeCategorySettingPolicy" name="group_cisco"> <parameter value="Cisco" key="category"/> <parameter value="ALL_PARAMETERS" key="matchBehavior"/> <parameter value=".1.3.6.1.4.1.9" key="sysObjectId"/> </policy> </policies> </foreign-source>