test_kubernetes_secondary_dns_basic_nslookup is always failing in full regression tier-2 tests (at least this is what we see in 4.20 runs), but passes locally (when executed against other clusters).
2 things to consider:
1.
The failure might be because of assigning a static IP from 10.200.x.y to the VM's secondary interface, but I am not 100% sure, because if this was the issue, then I would expect it to fail on setup (when `kubernetes_secondary_dns_vm_secondary_interface_ip` is looking for the interface in the VMI), and not on the test, when calling secondary_network_in_nslookup_output.

2.
timeout:
The documentation in `secondary_network_in_nslookup_output` says:

1. It can take up to 30 seconds for the IP address to be returned in the nslookup command (even if it already

so maybe an explicit `-timeout` argument should be sent when calling `nslookup`.