-
-
Notifications
You must be signed in to change notification settings - Fork 142
jira::facts don't work with All-in-One Puppet 4.x agent #151
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
Comments
thanks for reporting this. It would be very cool if you can spin up a PR. We should be able to review + merge + publish a fixed version in a short timeframe. |
I think that I figured out the logic to detect the AIO agent. Don't know if it will work with the AIO agent for PE. I don't have a way to test it on other version of puppet to see if still works with them. I can summit a PR to have you take a look at it. |
Looks like this was fixed by now. |
This is still a problem unless you have ruby installed on your system. If you are using the OSS version of Puppet |
Ah, so this is puppet-jira/manifests/facts.pp Lines 30 to 38 in 0f32b04
I'd suggest changing the check to |
Let me try to do it this weekend. I have a fork with this fixed for some time. I also have a dev environment to test it in. |
I have submitted the PR, but it looks like I need to update some of the tests too. I'm pretty sure that Puppet 5 and 6 only come in an AIO version. If that is the case in |
I think so yes. Since Puppet 4, Puppetlabs only ships AIO packages. |
The AIO agent moved its ruby to /opt/puppetlabs/puppet/bin/ruby. "PE" detection logic in jira::facts hasn't been adjusted for the AIO agent. As a result, on nodes with the AIO agent, jira_facts.rb exists at both /etc/facter/facts.d/ and /etc/puppetlabs/facter/facts.d, and neither has a path to ruby that works, so both report Facter errors on agent runs. I know that changing the shebang in jira_facts.rb to #!/opt/puppetlabs/puppet/bin/ruby fixes this. I will try to put in a PR with updated logic for the AIO agent.
The text was updated successfully, but these errors were encountered: