https://jira.akraino.org This file is an XML representation of an issue en-us 9.4.5 940005 11-04-2023 https://jira.akraino.org/browse/ICN-281 Integrated Cloud Native NFV <p>Wrong name server causes that vagrant vm cannot running correctly. <br/> systemd-resolved will set the nameserver to 127.0.0.53, which will not work correctly.<br/> It happened when your bare metal works behind a NAT and the vm image is 18.04+.</p> <p>Bare metal with Ubuntu-18.04-server behind a NAT</p> ICN-281

Vagrant vm can not get correct name server in ubuntu-1804.

Bug Medium Done Done Le Yao Le Yao icn-kud-r3 Mon, 24 Feb 2020 01:08:47 +0000 Thu, 17 Dec 2020 00:53:37 +0000 Tue, 25 Feb 2020 01:03:07 +0000 0 2 <p>Get it, but these two solution can not work with 'vagrant up installer'.<br/> The vm Installer uses nfs type to set synced_folder and the vm will install nfs client before the vm.provision shell scripts runs. That's to say the vm still use the wrong nameserver 127.0.0.53.</p> <p>The issue is with VM's to be created during Vagrant up or Vagrant up installer</p> <p>Solution 1:<br/> #!/bin/bashset -e<br/> echo "nameserver %{NATIP}" &gt;&gt; /etc/resolv.conf<br/> Solution 2: Could be <a href="https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87</a> adding this information inside Vagrantfile (<a href="https://github.com/onap/multicloud-k8s/blob/master/kud/hosting_providers/vagrant/Vagrantfile" class="external-link" target="_blank" rel="nofollow noopener">https://github.com/onap/multicloud-k8s/blob/master/kud/hosting_providers/vagrant/Vagrantfile</a>) instead of node.sh. </p> <p><a href="https://jira.akraino.org/secure/ViewProfile.jspa?name=r.kuralamudhan" class="user-hover" rel="r.kuralamudhan">r.kuralamudhan</a>: The broader question should be why aren't the 18.04 VMs getting created properly in my opinion. Solution 1 &amp; 2 could be a potential fix. However, this could be perceived as hardcoding the values inside the VM rather than debugging why aren't the VMs getting created fine with the correct nameserver information in the first place.</p> <p>Another patch may fix the issues:<br/> <a href="https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87" class="external-link" target="_blank" rel="nofollow noopener">https://gerrit.onap.org/r/c/multicloud/k8s/+/99540/2/kud/hosting_providers/vagrant/node.sh#87</a></p> <p>To solve it, you can add a shell script to Vagrantfile to set the name server manually.</p> <div class="code panel" style="border-width: 1px;"><div class="codeContent panelContent"> <pre class="code-bash"><span class="code-comment">#!/bin/bash </span>set -e echo <span class="code-quote-red">"nameserver %{NATIP}"</span> &gt;&gt; /etc/resolv.conf </pre> </div></div> <p>Some of the errors it caused:<br/> Stderr from the command:</p> <p>W: Failed to fetch <a href="http://us.archive.ubuntu.com/ubuntu/dists/bionic/InRelease" class="external-link" target="_blank" rel="nofollow noopener">http://us.archive.ubuntu.com/ubuntu/dists/bionic/InRelease</a> Temporary failure resolving 'us.archive.ubuntu.c om'<br/> W: Failed to fetch <a href="http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease" class="external-link" target="_blank" rel="nofollow noopener">http://us.archive.ubuntu.com/ubuntu/dists/bionic-updates/InRelease</a> Temporary failure resolving 'us.archive. ubuntu.com'<br/> W: Failed to fetch <a href="http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease" class="external-link" target="_blank" rel="nofollow noopener">http://us.archive.ubuntu.com/ubuntu/dists/bionic-backports/InRelease</a> Temporary failure resolving 'us.archiv e.ubuntu.com'</p> Blocks ICN-260 Development Rank 0|i003cg: Sprint ICN Sprint 12