-
Type:
Bug
-
Status: Resolved (View Workflow)
-
Priority:
Blocker
-
Resolution: Fixed
-
Affects Version/s: 18.0.2, Meridian-2016.1.3
-
Fix Version/s: 18.0.3, Meridian-2016.1.4
-
Component/s: Provisioning / Discovery / Importer
-
Security Level: Default (Default Security Scheme)
-
Labels:None
When adding nodes through auto-discover and the FQDN of the IP associated with the newSuspect is defined on DNS, the FQDN will be used for the node's label.
If the DNS is updated, the node's label is updated after a rescan.
Now, if the node is unreachable by the time Provisiond rescans the node (due to a regular scheduled rescan, or a forceRescan), the node's label is set to the IP of the node, which is not expected.
The FQDN (once it is saved correctly) should not be replaced by an IP. The only valid use case is when the DNS reports a different name.
