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

rake beaker errors with vagrant-puppet-install loaded #35

Closed
MikeCaspar opened this issue Jan 5, 2016 · 4 comments
Closed

rake beaker errors with vagrant-puppet-install loaded #35

MikeCaspar opened this issue Jan 5, 2016 · 4 comments

Comments

@MikeCaspar
Copy link
Contributor

Have been working on getting a sample rake beaker going.
At first,I believed it was a problem with my local app...
Tried downloading a sample project from puppetlabs.

My machine: ubuntu 14.04

Here are the steps to reproduce... (with vagrant-puppet-install already loaded and available).

  • vagrant uninstall plugin vagrant-puppet-install
  • clone a sample repo ie: (puppetlabs/puppetlabs-motd)
  • make no modifications
  • rake spec (works fine)
  • rake beaker (works fine)
  • vagrant installplugin vagrant-puppet-install
  • rake spec (works fine)
  • rake beaker... (exception)
/home/mike/.rvm/gems/ruby-2.2.4/gems/beaker-2.31.0/lib/beaker/hypervisor/vagrant.rb:196:in `block (2 levels) in vagrant_cmd': Failed to exec 'vagrant up'. Error was /home/mike/.vagrant.d/gems/gems/vagrant-puppet-install-3.0.0/lib/vagrant-puppet-install/action/install_puppet.rb:65:in `default_install_url': undefined method `match' for nil:NilClass (NoMethodError) (RuntimeError)
    from /home/mike/.vagrant.d/gems/gems/vagrant-puppet-install-3.0.0/lib/vagrant-puppet-install/action/install_puppet.rb:58:in `find_install_script'
    from /home/mike/.vagrant.d/gems/gems/vagrant-puppet-install-3.0.0/lib/vagrant-puppet-install/action/install_puppet.rb:16:in `initialize'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.rb:90:in `new'

The results were reproduced with ruby 1.9.3 (I thought I'd give that a try just in case).

Let me know if there's anything else I can do to help.

@glenjamin
Copy link
Contributor

I just hit this too, looks like the plugin doesn't handle puppet_version not being set.

Looks like an easy fix, PR incoming.

@christophepujol
Copy link

Hi!

I have the sale problem. I don't find a solution for this problem.

Please help me :)

@petems
Copy link
Owner

petems commented Jul 18, 2016

@christophepujol What version of vagrant-puppet-install are you on? Can you try ugrading for me?

@christophepujol
Copy link

Thanks. It's OK now :)

Le lun. 18 juil. 2016 13:52, Peter Souter notifications@github.com a
écrit :

@christophepujol https://github.com/christophepujol What version of
vagrant-puppet-install are you on? Can you try ugrading for me?


You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#35 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEhKPW4q9H7pT7Wm0v2Il11aEq7CYUjrks5qW2kWgaJpZM4G-iPn
.

Christophe PUJOL
06 51 38 84 05

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants