[ICN-285] Installer vm cannot install nfs because of nameserver issues. Created: 26/Feb/20  Updated: 17/Dec/20  Resolved: 21/Apr/20

Status: Done
Project: Integrated Cloud Native NFV
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Le Yao Assignee: Le Yao
Resolution: Done Votes: 0
Labels: icn-kud-r3
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Blocks
blocks ICN-260 KUD Multi Vagrant 18.04 issue Done
Sprint: ICN Sprint 14, ICN Sprint 16

 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.



 Comments   
Comment by Le Yao [ 07/Apr/20 ]

The patch is in review:
https://gerrit.onap.org/r/c/multicloud/k8s/+/104460

Generated at Sat Feb 10 05:58:42 UTC 2024 using Jira 9.4.5#940005-sha1:e3094934eac4fd8653cf39da58f39364fb9cc7c1.