Project

General

Profile

Bug #15043

mcollective puppetrun provider can't find puppet-agent mco binary

Added by Alex Fisher over 2 years ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Puppet
Target version:
Difficulty:
Triaged:
Bugzilla link:
Team Backlog:
Fixed in Releases:
Found in Releases:

Description

In puppet 4 (puppet-agent AIO packages) the location of the mco binary has changed.

The mcollective puppetrun provider tries to find the mco binary here.
https://github.com/theforeman/smart-proxy/blob/f9c9e7ad4183d26e4060ed85bf38d580b5c356bd/modules/puppet_proxy/mcollective.rb#L18
and fails.


Related issues

Blocks Foreman - Tracker #8447: Puppet 4 supportClosed2014-11-19

Associated revisions

Revision 67f82027 (diff)
Added by Alex Fisher over 2 years ago

fixes #15043 - Fix puppet 4 mco search path

In puppet 4, (AIO packaging), binaries can be found in
`/opt/puppetlabs/bin`.

(`/opt/puppetlabs/bin/mco` is actually a symlink to
`/opt/puppetlabs/puppet/bin/mco`, but `/opt/puppetlabs/bin` is what's
added to PATH in `/etc/profile.d/puppet-agent.sh` so is probably the
path that should be searched.)

History

#1 Updated by The Foreman Bot over 2 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/smart-proxy/pull/418 added

#2 Updated by Alex Fisher over 2 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Dominic Cleal over 2 years ago

  • Category set to Puppet
  • Assignee set to Alex Fisher
  • Legacy Backlogs Release (now unused) set to 136

#4 Updated by Dominic Cleal over 2 years ago

Also available in: Atom PDF