Skip to content
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

Issue with private network interface Vagrant >1.8.1 #7808

Closed
embano1 opened this issue Sep 17, 2016 · 3 comments
Closed

Issue with private network interface Vagrant >1.8.1 #7808

embano1 opened this issue Sep 17, 2016 · 3 comments

Comments

@embano1
Copy link

embano1 commented Sep 17, 2016

Hi,

discovered a weird behavior of Vagrant in versions >1.8.1 (1.8.1 working). vagrant up (multi-node Vagrantfile) throws:

==> manager: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ifconfig eth1 192.168.33.101 netmast 255.255.255.0

Stdout from the command:

Stderr from the command:

netmast: Unknown host
ifconfig: `--help' gives usage information.

Note the misspelled "netmast" command here...

Vagrant version

Run vagrant -v to show the version. If you are not running the latest version
of Vagrant, please upgrade before submitting an issue.

Host operating system

OSX 10.11.6

Guest operating system

VMware PhotonOS 1.0 (GA)

Vagrantfile

[...]

Corresponding config.vm.network parameter

config.vm.network "private_network", ip: opts[:eth1]

Expected behavior

Private network interface should be created as in Vagrant 1.8.1

Actual behavior

==> manager: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

ifconfig eth1 192.168.33.101 netmast 255.255.255.0

Stdout from the command:

Stderr from the command:

netmast: Unknown host
ifconfig: `--help' gives usage information.

@chrisroberts
Copy link
Member

Fixed via #7873. Thanks for the report!

@embano1
Copy link
Author

embano1 commented Oct 8, 2016

thank you!

gitebra pushed a commit to gitebra/vagrant that referenced this issue Oct 10, 2016
* commit 'd178631ff95bc07701fcabcfa33ad11eb9ab7ba3':
  Generic white space strip from command strings
  Update CHANGELOG
  Update CHANGELOG
  Revert "Fix incorrect ssh-config output when '--host' is defined"
  Update CHANGELOG
  Update CHANGELOG
  Fix typo (netmast => netmask) for Photon guest hashicorp#7808
  Fix incorrect ssh-config output when '--host' is defined
  Add test for provider priority fix
  Fix Vagrant not prioritizing configured providers correctly
@ghost
Copy link

ghost commented Apr 3, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants