But it should search its database to find the parent-foreign-id (or label) becouse - imho - it is very common, that routers etc. are in other requisition groups than server, but the server´s parent should point to the router for a working path-outage setup.
There was one more problem with the code... it wasn't passing the parent-foreign-source value into the ProvisionService API correctly. I've fixed this; the fix version will still be 1.10.3.
commit 531504bb771cf8cce4dbfda5ecaec81dc8fb2517
Seth Leger May 16, 2012 at 2:05 PM
I forgot to add the attribute to the XSD file which is apparently still in use by the import unmarshalling code. Marking as fixed again.
commit a1006b251c1223aa781c29e35d35c5731a61b8a2
Seth Leger May 16, 2012 at 2:01 PM
Based on testing, this issue was not fixed properly. Reopening.
Andy Ellsworth May 7, 2012 at 4:52 PM
Does this perchance fix (or provide an operational workaround) for []?
Seth Leger April 10, 2012 at 4:06 PM
I've added the attribute suggested by Ben (parent-foreign-source). The default value will be the foreign-source of the current requisition but if you specify the attribute, you can point nodes at parents that are in a different foreign source. Marking as fixed.
http://www.opennms.org/documentation/java-xsddocs-stable/model-import.html#element_node
defines two parameter for path-outage, but parent-foreign-id and parent-node-label parameter work only if the parent-foreig-id/label is in the same requisition group as the node.
But it should search its database to find the parent-foreign-id (or label) becouse - imho - it is very common, that routers etc. are in other requisition groups than server, but the server´s parent should point to the router for a working path-outage setup.