Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

importing a provisioning group erases path outages

Description

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.

Environment

Operating System: Linux Platform: PC

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Seth Leger November 13, 2014 at 4:19 PM

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 https://opennms.atlassian.net/browse/NMS-4842#icft=NMS-4842 - 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.

Won't Fix

Details

Assignee

Reporter

HB Backlog Status

Components

Fix versions

Affects versions

Priority

PagerDuty

Created February 17, 2010 at 3:20 AM
Updated September 1, 2020 at 3:03 PM
Resolved September 1, 2020 at 3:03 PM

Flag notifications