wsilva / kubernetes-vagrant

Project that facilitates the creation of a multinode Kubernetes cluster using Vagrant, Virtualbox and we running Ubuntu for study purposes.

• English 🇺🇸
• Portugues (Brasil) 🇧🇷

kubernetes-vagrant's Issues

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Rodei

vagrant init
up --provision

e estou recebendo este erro:

$ vagrant up k8smaster --provision
Bringing machine 'k8smaster' up with 'virtualbox' provider...
==> k8smaster: Checking if box 'ubuntu/bionic64' version '20190724.1.0' is up to date...
==> k8smaster: Clearing any previously set forwarded ports...
==> k8smaster: Clearing any previously set network interfaces...
==> k8smaster: Preparing network interfaces based on configuration...
    k8smaster: Adapter 1: nat
    k8smaster: Adapter 2: hostonly
==> k8smaster: Forwarding ports...
    k8smaster: 22 (guest) => 2222 (host) (adapter 1)
==> k8smaster: Running 'pre-boot' VM customizations...
==> k8smaster: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "2a47452b-178b-470f-89bd-ddc6252462a4", "--type", "headless"]

Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole


AzureAD+IgorMonteiroVieira@Igor MINGW64 ~/Desktop/kubernetes-vagrant (master)
$ vagrant up k8smaster --provision

Entao, vi que a placa de rede está como Host-Only:

Segue meu Vagrant file:

Vagrantfile.zip

$ vagrant global-status
id       name      provider   state    directory                                           
----------------------------------------------------------------------------------------------
e7ab9e6  k8smaster virtualbox poweroff C:/Users/IgorMonteiroVieira/Desktop/kubernetes-vagrant

The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date (use "vagrant global-status --prune" to prune invalid
entries). To interact with any of the machines, you can go to that
directory and run Vagrant, or you can use the ID directly with
Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"

k8smaster: SSH auth method: private key, Net::SSH::ConnectionTimeout

$ vagrant up --provision
Bringing machine 'k8smaster' up with 'virtualbox' provider...
Bringing machine 'k8snode1' up with 'virtualbox' provider...
Bringing machine 'k8snode2' up with 'virtualbox' provider...
==> k8smaster: Checking if box 'ubuntu/bionic64' version '20190724.1.0' is up to date...
==> k8smaster: Clearing any previously set forwarded ports...
==> k8smaster: Clearing any previously set network interfaces...
==> k8smaster: Preparing network interfaces based on configuration...
    k8smaster: Adapter 1: nat
    k8smaster: Adapter 2: hostonly
==> k8smaster: Forwarding ports...
    k8smaster: 22 (guest) => 2222 (host) (adapter 1)
==> k8smaster: Running 'pre-boot' VM customizations...
==> k8smaster: Booting VM...
==> k8smaster: Waiting for machine to boot. This may take a few minutes...
    k8smaster: SSH address: 127.0.0.1:2222
    k8smaster: SSH username: vagrant
    k8smaster: SSH auth method: private key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.