Installer vm cannot install nfs because of nameserver issues.
Description
When executing command 'vagrant up installer', it will hang on the step '==> installer: Installing NFS client...', because of the 127.0.0.53 nameserver. And this step executes before the vm.provision shell scripts, so the patch and sollution in icn-281 won't work for it.
Root Cause: The vm named installer use nfs to sync folder (multi-k8s file) with host. It will install nfs-client in vm. But this installation will be executed before the vagrant vm provision runs. This means the nameserver solution scripts runs after the nsf-client installation, so the broken network works for nfs-client-installtion and cause errors.
When executing command 'vagrant up installer', it will hang on the step '==> installer: Installing NFS client...', because of the 127.0.0.53 nameserver. And this step executes before the vm.provision shell scripts, so the patch and sollution in icn-281 won't work for it.
Root Cause:
The vm named installer use nfs to sync folder (multi-k8s file) with host. It will install nfs-client in vm.
But this installation will be executed before the vagrant vm provision runs. This means the nameserver
solution scripts runs after the nsf-client installation, so the broken network works for nfs-client-installtion and cause errors.