Discovery leaves an invalid/removed IP address in the main device CI attribute, without updating it to a newly discovered IP. (discovery.device.complete event is not getting fired) - Known Error

Discovery leaves an invalid/removed IP address in the main device CI attribute, without updating it to a newly discovered IP. (discovery.device.complete event is not getting fired) Description Discovery can leave an old invalid/retired IP address in the IP address attribute/field of the main device CI [e.g. cmdb_ci_win_server, or others]. The IP address related list [cmdb_ci_ip_address] will still be correctly updated to remove the invalid/absent IP.

This problem was introduced by the fixes of PRB1343838 and then PRB1380126 to prevent the main CI's IP address field being changes and changed back. That flapping value issue had to be fixed due to the side-effects related to the spamming of the audit history of the CI, but has resulted in the value not being changed even when it needs to be.

This can happen in the following scenarios:

A device that has a single IP, which is set by DHCP, and regularly changes automatically, or is manually changed. A device that has multiple IPs (and network adapters), and the IP that is entered in the main CI is removed and now absent from the device Expected behaviour:

The IP address entered on the main device CI should not be changed by Discovery if it is still one of the valid IPs of the device, even if the IP address Discovery is doing the scan via is not the same one. If the IP address entered on the main device CI is no longer seen in the device's configuration by a discovery scan, and is set as absent in the IP address table, then the main CI attribute should be updated to another valid IP instead, usually the IP being scanned at the time. Steps to Reproduce

Discover a device Validate that the discovered device IP Address attribute on the device CI is the IP you used for discovery, Reconfigure the device with a different IP address Rediscover the same with the new IP address The Device should reconcile, and the IP Address attribute of the device CI should be updated.

What happens is the old IP remains in the main CI IP Address attribute.

Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

Partial Workaround (this reverts the PRB1380126 fix for the IP address field value flapping, and double update):

Navigate to Discovery Definition -> Sensors Edit the file "Horizontal Discovery Sensor" Replace the line that calls the prevention of IP flapping (should be line 167, but can differ): var ireIdentityTime = resultHandler.preventFlappingAttributeOnParentClassReturnIreTime(apiPayload, 'cmdb_ci_hardware', 'ip_address', false); Replaced with: var ireIdentityTime = 0; Save Make sure you mark the file for future upgrade, or remember to revert the file to out-of-box after the Rome upgrade.