-
Notifications
You must be signed in to change notification settings - Fork 4.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Network is unrealiable in generic/ubuntu1804 box #11256
Comments
Hey there @Wenzel - Since you mentioned you didn't think it was Vagrant but the box configuration you are using, please open an issue with the Generic group who maintains those boxes. You can find the repository here: https://github.com/lavabit/robox If it's actually an issue with Vagrant feel free to ping us on here or open a new issue, thanks! |
@briancain thanks for the link, will open an issue there ! |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
Vagrant version
Vagrant 2.2.6
Host operating system
Windows 10 build
1909
Guest operating system
generic/ubuntu1804
Vagrantfile
Please look at the following repository:
https://github.com/Wenzel/vagrant-oswatcher
Provider:
Hyper-V
Debug output
I don't believe Vagrant's debug log are useful here,
since the box configuration seems to be the root cause of this issue.
Expected behavior
The box should have been provisionned without any issues.
Actual behavior
The Ansible playbook systematically fails because of a network issue:
Temporary failure resolving us.archive.ubuntu.com
400 bad request
404 not found
Or even before the Ansible playbook is executed, the network fails.



And if it manages to execute the playbook, it systematically fails here:

I had to add a
retry
statement in my Ansible task to force retry until the network is reachable:Result:

Steps to reproduce
git clone https://github.com/Wenzel/vagrant-oswatcher
git clone https://github.com/Wenzel/oswatcher
vagrant-oswatcher/Vagrantfile
and set the local path to oswatcher's repovagrant up --provider hyperv
Note: I suppose the Vagrant team manages
generic
boxes on Vagrant's Cloud.Thanks !
The text was updated successfully, but these errors were encountered: