Closed jvanderaa closed 3 years ago
@jvanderaa Please provide us with exact logs of this issue - without a traceback I can not resolve this issue
This is a warning message and should not prevent the task from running.
Existing devices are identified by IP lookups against primary_ip4__address__net_host
. This function currently does not work with FQDNs and this was the initial intention. I am open for seeing a PR with this function :-)
Environment
Steps to Reproduce
['Invalid IP address format: rtr-branch']
Expected Behavior
Onboarding to occur
Observed Behavior
['Invalid IP address format: rtr-branch']