You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After the initial setup of the machines, I ran the debops command inside the machines which would modify /etc/issue. After shutting down the machine, a vagrant up resulted in an error:
$ vagrant up webmail
Bringing machine 'webmail' up with 'lxc' provider...
==> webmail: Checking if box 'debian/jessie64' is up to date...
==> webmail: Setting up mount entries for shared folders...
webmail: /vagrant => /home/ganto/vagrant/vagrant-projects/debops-jessie64-mailer-lxc
==> webmail: Starting container...
==> webmail: Waiting for machine to boot. This may take a few minutes...
webmail: SSH address: 192.168.123.254:22
webmail: SSH username: vagrant
webmail: SSH auth method: private key
==> webmail: Machine booted and ready!
==> webmail: Setting hostname...
==> webmail: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
An error occurred while executing the action on the 'webmail'
machine. Please handle this error then try again:
Vagrant attempted to execute the capability 'change_host_name'
on the detect guest OS 'linux', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.
An error occurred while executing the action on the 'mail'
machine. Please handle this error then try again:
Vagrant attempted to execute the capability 'change_host_name'
on the detect guest OS 'linux', but the guest doesn't
support that capability. This capability is required for your
configuration of Vagrant. Please either reconfigure Vagrant to
avoid this capability or fix the issue by creating the capability.
Expected behavior
Machine should properly be detected as Debian Linux.
Actual behavior
The OS detection mechanism of Vagrant failed because /etc/issue within the machine is not the original file shipped by Debian anymore:
This commit introduces the salt_arg option that allows a user to pass
additional command line flags to the `salt` tool when provisioning with
a master setup.
It also adds additional config validation to ensure that both
`salt_args` and `salt_call_args` is an array.
briancain
added a commit
to briancain/vagrant
that referenced
this issue
Aug 29, 2017
This commit introduces the salt_arg option that allows a user to pass
additional command line flags to the `salt` tool when provisioning with
a master setup.
It also adds additional config validation to ensure that both
`salt_args` and `salt_call_args` is an array.
ghost
locked and limited conversation to collaborators
Apr 4, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Vagrant version
Vagrant 1.8.5
Host operating system
Gentoo
Guest operating system
Debian Jessie
Vagrantfile
Error Message
After the initial setup of the machines, I ran the
debops
command inside the machines which would modify/etc/issue
. After shutting down the machine, avagrant up
resulted in an error:Expected behavior
Machine should properly be detected as Debian Linux.
Actual behavior
The OS detection mechanism of Vagrant failed because
/etc/issue
within the machine is not the original file shipped by Debian anymore:Steps to reproduce
/etc/issue
in the machine that it won't contain the wordDebian
anymoreThe text was updated successfully, but these errors were encountered: