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

Old asset field "maintContractNumber" in legacy requisitions breaks provisioning after uprading to 1.10

    XMLWordPrintable

    Details

      Description

      In OpenNMS 1.8, there was an asset field named "maintContractNumber". In OpenNMS 1.10, this field's name was shortened to just "maintContract".

      The database changes are handled automatically, but it seems we missed the case where a user still has requisitions (either static on disk or dynamically generated) that use the old name for this field. Because of a long-standing bug in Provisiond, the presence in a requisition of an invalid asset record field name causes the synchronization of the entire requisition to abort silently. When this happens, the most obvious symptom is that all physical interfaces disappear from the nodes defined in the requisition.

      Not sure what to do about this, but it's impacting at least one support customer (see https://mynms.opennms.com/Ticket/Display.html?id=1065) so we need to do something about it.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                seth Seth Leger
                Reporter:
                jeffg Jeff Gehlbach
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: