Uploaded image for project: 'Integrated Cloud Native NFV'
  1. Integrated Cloud Native NFV
  2. ICN-285

Installer vm cannot install nfs because of nameserver issues.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Priority: Medium
    • Resolution: Done
    • Labels:
    • 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.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              iProg Le Yao
              Reporter:
              iProg Le Yao
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: