While invalid IP addresses should not make their way into a requisition, in the case that they do, the provisiond cycle will stop processing subsequent nodes in the requisition. When encountering an invalid IP, that node (or just that IP) should be skipped to allow other nodes in the requisition to complete the import cycle.

When importing a requisition from a non-file source (such as an HTTP location), there should be an additional check for IP validity and omit/log invalid IP addresses to prevent them from being written to the requisition file.

Invalid IP addresses are only written to provisiond.log when in DEBUG mode. Including invalid IP addresses in WARN mode will help users identify the issue in a timely manner. And after PRIS-157 and https://opennms.atlassian.net/browse/NMS-13805#icft=NMS-13805, should have a lower chance of making their way into a requisition.