-
Notifications
You must be signed in to change notification settings - Fork 12
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
Problems with plugin sync #2
Comments
@frizop how is Puppet installed on your system, using the OS packes or via ruby gem? I'll point you to the Installation section of README.md - https://github.com/jantman/vagrant-r10k#installation Puppet is specifically not included in the plugin itself, as that would conflict with any existing puppet installs on the system. If you have the puppet gem installed (what does the output of I can try to reproduce this on my own machine in the morning or tomorrow. |
Ahh, I just saw what might be the key here:
I haven't tested this with rbenv, as I don't use it and don't believe I know anyone who does. I'll need some time tomorrow morning to try and reproduce this and see what I can do. |
Yep, you got it. I end up just building everything via ruby gems because I find it a bit easier to manage that way rather than pulling down packages and installing them over each other. Just for clarity sake, here is a list of the gems installed on my system: Oh and one note, using the system ruby on the mac os is just asking for pain, thus the use of rbenv. I'm tied to
|
Ok. I'll have to spend some time on this to see how to reproduce it and get a fix (not familiar with rbenv), but if you happen to have any suggestions on that, I'm open to them. If not, I'll see what I can come up with tomorrow. Thanks for taking the time to provide a thorough, detailed bug report. |
@frizop I'm really sorry, but I haven't had time to really look into this yet, and I'm about to be leaving for a week without reliable Internet access. I can, however, provide you with a workaround that might work for your purposes; if you specify the modules in the Puppetfile using their git repos instead of Forge modules, git will be used to install them instead of So, this would mean taking your current Puppetfile:
and changing it to use git repos as the module source:
Usually I would specify the ref for each of them, to ensure that I use a tag that matches up to a specific released version of the module (and to prevent pulling in any possibly-un-released changes from master), but neither of the two non-puppetlabs modules you're using appear to be properly tagging their releases on GitHub. |
Ah, right on. Tested and this does indeed work. Any chance you could help point to what's wrong and maybe I can also take a look? I'm no ruby dev but I'll give it the ol' college try. Also, I was away on vacation myself so no worries about not having an immediate solution! |
I did note one thing looking into this a little bit, when running a debug2 on the r10k module running a module install, and it's that the R10K::Task::Module::Sync gets called, where I only see a R10K::Task::Puppetfile::Sync getting called on the vagrant module. I'm having a little bit of trouble following the application flow of the r10k module, it might be a little over my head or at least I don't know the proper debugging tools for ruby to really get my teeth into it.
|
I've got a similar error and what I understand it is we can't have puppet and puppet gem installed at the same time? The workaround for me is the same as mentionned above: avoid using Puppet Forge directly. |
@tremblaysimon The puppet gem isn't included in this plugin as doing so can cause conflicts on systems where Puppet is already installed (i.e. via os packages). For the time being, yes, if you specify the modules directly from git or other source control (instead of as forge modules), it will prevent this issue. |
I've got the same problem, having three versions of puppet installed (3.6.2, 3.7.4, 3.7.5) with rubygem. I've removed them and installed 3.7.5 from the puppetlabs debian repo, the problem disappeared. Thanks |
@lorello I was using gems as well but ended up giving up and just installing the packages from puppetlans directly, no more problems. I'd love to know why but I don't have the time to debug this or really worry about it. |
Er so... If I am understanding this thread correctly -- Forge modules cannot be referenced from a Puppetfile still? I'm having this issue and do not want to reference the git repos directly. I have one version of the puppet gem (4.2.0) installed on my OSX 10.10.3 host. |
I seem to have been able to get it to work by doing..
Sorry for the interruption! |
@mmarod, I'd completely forgotten that you can use |
When trying to launch a
vagrant up
and using config elements like the following, I get the error in the debug log -and the following Puppetfile
The short of the error is the following
So I'm pretty confused here, if I manually run the puppet module command above it works fine, if I run
r10k puppetfile install
it installs fine, but for some reason (even after uninstalling and reinstalling the vagrant r10k plugin) it still doesn't work, any help?And the debug log:
The text was updated successfully, but these errors were encountered: