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

Vagrant-Coreos: Every vagrant cli command raises "Installing vagrant-ignition" #2494

Open
kzpm opened this Issue Aug 14, 2018 · 3 comments

Comments

Projects
None yet
2 participants
@kzpm

kzpm commented Aug 14, 2018

Issue Report

Bug

Container Linux Version

Not able to execute vagrant ssh, so no means to extract version on guest system.

$ cat /etc/os-release
NAME="Debian GNU/Linux"
VERSION="9 (stretch)"
...
BUG_REPORT_URL="https://issues.coreos.com"

Environment

What hardware/cloud provider/hypervisor is being used to run Container Linux?

  • Vagrant provider: VirtualBox

Expected Behavior

vagrant up command should result in creation of 3 machines

Actual Behavior

  • vagrant up and nearly every command issued with "vagrant" leads to a iteration of messages showing "Installing plugins: vagrant-ignition"
  • The creation of 3 machine-instances, as defined in config.rb fails

Reproduction Steps

execute "vagrant up" on cli

Other Information

I have included my Vagrantfile, config.rb and user-data. If you need more info I'm glad to provide!

config.rb.txt
user-data.txt
Vagrantfile.txt

@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 15, 2018

Member

@kzpm please check the node console in virtualbox. The user-data you attached is not an ignition JSON config, so it is possible that the nodes are simply stuck due to failed provisioning.

For more information, see https://github.com/coreos/coreos-vagrant/#provisioning-with-ignition-virtualbox-provider-default.

Member

lucab commented Aug 15, 2018

@kzpm please check the node console in virtualbox. The user-data you attached is not an ignition JSON config, so it is possible that the nodes are simply stuck due to failed provisioning.

For more information, see https://github.com/coreos/coreos-vagrant/#provisioning-with-ignition-virtualbox-provider-default.

@kzpm

This comment has been minimized.

Show comment
Hide comment
@kzpm

kzpm Aug 15, 2018

Thanks to the tip from Nuxy in the thread hashicorp/vagrant#8055 the iteration stops and proceeds seemingly normal.
Now it is possible to issue vagrant commands again.

I replaced in Vagrantfile:

plugins_to_install = required_plugins.select { |plugin| not Vagrant.has_plugin? plugin }

if not plugins_to_install.empty?
  puts "Installing plugins: #{plugins_to_install.join(' ')}"
  if system "vagrant plugin install #{plugins_to_install.join(' ')}"
    exec "vagrant #{ARGV.join(' ')}"
  else
    abort "Installation of one or more plugins has failed. Aborting."
  end
end

with:

required_plugins = %w[vagrant-plugin-1 vagrant-plugin-2 vagrant-plugin-3]

return if !Vagrant.plugins_enabled?

plugins_to_install = required_plugins.select { |plugin| !Vagrant.has_plugin? plugin }

if plugins_to_install.any?
  system "vagrant plugin install #{plugins_to_install.join(' ')}"
  exit system 'vagrant up'
end

kzpm commented Aug 15, 2018

Thanks to the tip from Nuxy in the thread hashicorp/vagrant#8055 the iteration stops and proceeds seemingly normal.
Now it is possible to issue vagrant commands again.

I replaced in Vagrantfile:

plugins_to_install = required_plugins.select { |plugin| not Vagrant.has_plugin? plugin }

if not plugins_to_install.empty?
  puts "Installing plugins: #{plugins_to_install.join(' ')}"
  if system "vagrant plugin install #{plugins_to_install.join(' ')}"
    exec "vagrant #{ARGV.join(' ')}"
  else
    abort "Installation of one or more plugins has failed. Aborting."
  end
end

with:

required_plugins = %w[vagrant-plugin-1 vagrant-plugin-2 vagrant-plugin-3]

return if !Vagrant.plugins_enabled?

plugins_to_install = required_plugins.select { |plugin| !Vagrant.has_plugin? plugin }

if plugins_to_install.any?
  system "vagrant plugin install #{plugins_to_install.join(' ')}"
  exit system 'vagrant up'
end
@lucab

This comment has been minimized.

Show comment
Hide comment
@lucab

lucab Aug 16, 2018

Member

@kzpm glad that you solved it. Reading the other bug report, it sounds like an issue mostly related to the host environment. Which OS/release are you using?

Member

lucab commented Aug 16, 2018

@kzpm glad that you solved it. Reading the other bug report, it sounds like an issue mostly related to the host environment. Which OS/release are you using?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment