Raising to critical since several bugs have been opened regarding this issue.
Andy Ellsworth September 12, 2011 at 5:05 PM
IMO, this is a similar issue to - until it's "proper fixed", end users need some kind of warning not to edit node properties of provisioned nodes anywhere outside of the requisition.
David Hustace September 12, 2011 at 2:51 PM
So, we need to know the exact behavior. If using Provisiond, don't use the Create Path outages GUI?
Benjamin Reed August 23, 2011 at 1:05 PM
After a discussion on IRC, it sounds like the real issue is that the path-outages web UI is not provisiond-aware. It should either not let you edit provisioned nodes (instead pointing to the requisition editor), or should update the requisition while it's updating the node.
Dominik February 17, 2010 at 3:38 AM
Sorry, by setting parent-foreign-id, it is possible to configure a path outage within the xml.
Whenever provisiond imports the nodes from a provisioning group, the configured path outages for those nodes are deleted from the database.
Looking at http://xmlns.opennms.org/xsd/config/model-import I could not find a way to configure a pathoutage within the xml definitions, so here's the bug.