-
Notifications
You must be signed in to change notification settings - Fork 32
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
Compile error - no such file to load puppet_x/gms/type #33
Comments
@rjhornsby the required file is here: https://github.com/abrader/abrader-gms/blob/master/lib/puppet_x/gms/type.rb You sure it's on your master in the correct location? If so, please provide the full stack trace. Also, keep in mind I've only ever said this module would work on Puppet 3.2 or later. I'll do the best I can to help. |
Sorry I should have been more clear, we are running puppet 4.5.1 (seeing same issue on 4.4.1 if it matters). "2.4.0" referred to what Attaching the stacktrace as requested. The file is definitely present (tree below). It's weird, like ruby just isn't able to find it. The permissions on the file look fine as well.
|
I'm seeing the same issue on puppet 4.7.0:
|
Same here, FOSS 4.7.0 on CentOS7, gms deployed by r10k to the correct path:
|
Well, I ended up implementing a gitlab custom_hooks/post-recieve triggering r10k via sudo. ugly but works. still, I'd love to get this working if I can. seems like the more elegant solution. |
@seefood @simmerz @rjhornsby All FOSS? What version of Ruby? Back from Puppetconf so I can take a look. |
Yes, FOSS Puppet. I can only assume the version of Ruby is whatever ships/embeds with Puppet 4.5.1 but I don't recall what Ruby version that is. Sorry I can't be more help, I recently switched to the dark side (chef) at a new gig. |
All FOSS and bundled ruby with puppetlabs puppet debs |
@simmerz I am not seeing the issue in the multiple versions of PE I've tested thus far today. Which PE version(s) can you confirm you've seen the issue arise? |
It's not PE, it's FOSS. |
I'm not using PE, I'm using FOSS. Latest stable for Ubuntu Xenial. On Tue, 25 Oct 2016, 20:06 Andrew Brader, [email protected] wrote:
Tomislav Simnett |
Any chance you remember what you implemented as a workaround? It seems I've re-introduced this issue recently after running some OS and puppet agent updates. |
I'm seeing the same on Puppet 4.8.2 / Puppetserver 2.7.2. Using the FOSS AIO packages. |
@abrader, any update on this? |
@abrader Is there a work around for this while we wait for the fix to be released or can you point me to a commit that this has been addressed in? |
@bmarshallbri I am working on code now which will fix this matter. I have some testing to complete as well. Could be a couple weeks. Best answer I can give you unfortunately. |
I ended up resolving this by appending an additional ruby path in the file below (the second entry is what I added). puppetserver.conf: ruby-load-path: [/opt/puppetlabs/puppet/lib/ruby/vendor_ruby,/opt/puppetlabs/puppet/modules/gms/lib] |
Also running into this error, version FOSS 4.10.1. Sounds like the official fix might be a bit backlogged, anyone have a fork/tweak they could recommend in the meantime? |
any news on this issue, I am using puppet 4.10 on Debian 8 and still has this problem, using bmarshallbri workaround solved my problem. |
FYI. Running puppet generate types for the environment has fixed this issue for me. I am adding this command to my r10k deploy webhook. |
Having a difficult time compiling a catalog on puppetserver 2.4.0 (FOSS). I'm sure that gms 1.0.3 worked previously, because I upgraded to fix the minor permissions issue in 1.0.2.
A puppet run throws an error compiling the catalog containing gms:
The reference to line 29 is this block in the puppetmaster profile:
From looking at the puppetserver logs, it looks like the issue is the require line in
gms/lib/puppet/type/git_deploy_key.rb
The top of the stacktrace points here
Just in case I messed something up, I wiped gms from the modules directory and wiped r10k's cache (and redeploying the env), and also tried unpacking the module from a github-downloaded zip file into the modules directory. Same result.
It seems as if maybe there's a ruby search path issue here, but I'm not advanced enough yet to understand how to fix it.
The text was updated successfully, but these errors were encountered: