Uploaded image for project: 'OpenNMS'
  1. OpenNMS
  2. NMS-4379

Provisioner always punts on deleteService events when discovery not enabled

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Blocker
    • Resolution: Fixed
    • 1.8.7
    • 1.8.8, 1.9.4
    • Security Level: Default (Default Security Scheme)
    • A 1.8.7 system with Capsd turned off and discoveryEnabled set false (the default for this release) in opennms.properties

    Description

      Reference commercial support ticket #3853.

      Steps to reproduce:

      1. Create a requisition with a single node, single interface, at least one service on that interface
      2. Import the requisition
      3. In web UI, go to Node List -> NewNode -> click on any of the services -> Delete

      Expected result:
      Provisioner deletes the service

      Observed results:
      deleteService event is created and logged, but the service is unaffected.

      Suspected cause:
      Provisioner.handleDeleteService method has no reachable code when discoveryEnabled is false. Matt indicated in an IM exchange that he thinks this is not the case in 1.9.

      Attachments

        Activity

          People

            brozow Matt Brozowski (Inactive)
            jeffg Jeff Gehlbach
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: