Issues
- Update Provisiond scan to remove old primary IP intefaceNMS-16347Resolved issue: NMS-16347Christian Pape
- allow provisiond policies to apply to requisitioned interfacesNMS-16062
- Provisioning policies do not applyNMS-16031Resolved issue: NMS-16031Benjamin Reed
- snmp asset provisioning adapter throws exceptions when unable to reach SNMPNMS-15830
- Allow services to be deleted when they're removed from a requisition's foreign source definition and/or policiesNMS-15263
- Meta-Data not retained with periodic imports from external requisitionsNMS-14780Resolved issue: NMS-14780
- Provisiond threads description discrepanciesNMS-14766Resolved issue: NMS-14766Mark Mahacek
- "Requisition" misspelled as "requistion" in code and documentationNMS-14656
- VMware requisition import fail with "Problem getting input stream: '{}'"NMS-14450Resolved issue: NMS-14450Christian Pape
- Invalid node Foreign ID not checked during provisioning resulting in various RRD graphing problemsNMS-14142Resolved issue: NMS-14142Alex May
- Provisiond Fails to Start when wrong data is successfully POSTed via REST to hardwareInventory endpointNMS-14085Resolved issue: NMS-14085Pushkar Suthar
- Provisiond does not use the rescan-existing attribute from provisiond-configuration.xmlNMS-14023Resolved issue: NMS-14023Freddy Chu
- Instrument Provisiond Thread PoolsNMS-13969Resolved issue: NMS-13969Freddy Chu
- Improve handling of invalid IP addresses during provisioning cycleNMS-13806Resolved issue: NMS-13806Alex May
- Uncatched exception when importing a VMware virtual machine without an IP interfaceNMS-13781Resolved issue: NMS-13781Christian Pape
- No information when scheduled outage lost nodeNMS-13756
- vmwarereqtool does not retain metadataNMS-13171Resolved issue: NMS-13171Christian Pape
- unable to add node/interface meta-data through requisition uiNMS-13118Resolved issue: NMS-13118Christian Pape
- Vmware-importer requisition meta-data lost at importNMS-13109Resolved issue: NMS-13109Christian Pape
- Exception messages during node import (log noise)NMS-13082Resolved issue: NMS-13082Zoë Knox
- RRD files for SNMP data are not created until a Service RestartNMS-12974Resolved issue: NMS-12974Chandra Gorantla
- Node naming issues in provisioning process when using discoverydNMS-12440
- Discovery and foreignSource service detection get in the wayNMS-12411Resolved issue: NMS-12411Chandra Gorantla
- ReST API Resource for Provisiond ConfigurationNMS-12254
- WsMan Asset Adapter should handle WQL filters returning more than one resultNMS-10683Resolved issue: NMS-10683Jesse White
- WsMan Asset Adapter config contains an invalid resourceUriNMS-10682Resolved issue: NMS-10682Jesse White
- HwEntityAlias fails to be persistedNMS-10606Resolved issue: NMS-10606David Smith
- re-ip nodes is proving to be much more difficult than necessaryNMS-10531
- SNMP Authentication DiscoveryNMS-10513Resolved issue: NMS-10513
- Provisiond import errors don't appear as event reasonNMS-10469Resolved issue: NMS-10469Francesco Buccini
- Unable to remove asset data from provisioned nodesNMS-10456
- broken xml code in foreign source/imports is not being detectedNMS-10426Resolved issue: NMS-10426Christian Pape
- Support provisioning asset information via wsmanNMS-10404Resolved issue: NMS-10404Dino Yancey
- Discovery UI should not allow selection of Minions as Foreign SourceNMS-10400Resolved issue: NMS-10400Jeff Gehlbach
- Add Configurable Timeouts to VMware vCenter DiscoveryNMS-10377Resolved issue: NMS-10377Christian Pape
- Erroneous INFO-level log messages during every forced node rescanNMS-10370Resolved issue: NMS-10370Brynjar Eide
- DefaultProvisionService logs noisily for monitored service having state "N"NMS-10291Resolved issue: NMS-10291Jeff Gehlbach
- provisiond log complains about PasswordStrategyNMS-10216
- Missing event when setting interface to unmanagedNMS-10174
- IPInterfacePolicyMatch should be effective on discoved ipNMS-10154Resolved issue: NMS-10154
- Add filtering to provisioning adapter to ignore hardware inventory on devices that do not support ENTITY-MIBNMS-10151Resolved issue: NMS-10151
- Node label accepts ampersand (&) symbol, but it breaks graphingNMS-9904Resolved issue: NMS-9904Christian Pape
- Discovery uses Detectors in Default FS definition not those defined in the requisitionNMS-9874
- Improve provisioning adapters to support locations for minionsNMS-9851
- filters for hardware inventoryNMS-9844
- PostgreSQL jdbc detector fails with: java.lang.ClassNotFoundException: org.postgresql.Driver not foundNMS-9829Resolved issue: NMS-9829Chandra Gorantla
- Performance issues after upgrading from Horizon 18.0.x to 21.0.2NMS-9826Resolved issue: NMS-9826Jeff Gehlbach
- Allow users to delete a service from the systemNMS-9822
- Cannot synchronize nodes in provisioning requisition with databaseNMS-9714
- VMWare Importer: The rule for selecting the primary interface on VMs is not correctNMS-9713
50 of 823
During a primary interface IP direct replacement in the requisition, it’s observed that dbonly scan and periodic scan don’t remove the old IP interface from the node. With a manual requisition synchronization or force node scan, it does indeed remove the old IP interface from the node. Adding discovered IP interfaces works regardless of the type of scans.
Steps to reproduce
Replace IP primary interface of a node in the requisition.
Synchronize requisition (dbonly).
Wait for the periodic scan to take place.
After the periodic scan, the new IP primary interface is provisioned. However, the old IP primary interface remains in the node. At this point, the old IP interface has already been removed from the device so it shouldn't be discovered by Provisiond. Only when a manual scan is performed, then it removes the old IP primary interface from the node.
Expected outcome
dbonly scan should remove the old IP interface in addition to adding the new IP interface. It should only persists the IP addresses that exists in the requisition and remove the IP interfaces from the node that’s not in the requisition.
periodic scan should remove and add interfaces based on the current entries in the SNMP ipAddrTable. It should persists the IP addresses that exists in the table and remove the IP interfaces from the node that’s not in the table.