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 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.