Project

General

Profile

Actions

Bug #3012

closed

Mcollective does not need sudo to work properly

Added by Jasper Poppe almost 11 years ago. Updated almost 3 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
Puppet
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

Mcollective will always run with sudo, see: lib/proxy/puppet/mcollective.rb. When MCollective is configured properly, sudo is not needed to run the MCollective client.

I suggest:
1) Remove the following line from lib/proxy/puppet/mcollective.rb:
cmd.push(which("sudo", "/usr/bin"))

2) Implementing option 1 will probably break mcollective support for people who configured MCollective in such a way that sudo is needed. Instead of removing the sudo line it would be nice to have a parameter which enables/disables the sudo command for mcollective.


Related issues 1 (0 open1 closed)

Related to Smart Proxy - Feature #3150: foreman-proxy support for invoking sudo as a different user for mcollectiveClosedGreg Petras09/25/2013Actions
Actions #1

Updated by Dominic Cleal almost 11 years ago

  • Project changed from Foreman to Smart Proxy
  • Category changed from Smart Proxy to Puppet
Actions #2

Updated by Greg Petras over 10 years ago

As Jasper mentioned, this will break MCollective for people who need the sudo piece. We're using Puppet Enterprise, which automatically sets up everything for MCollective under the peadmin account. I opened an issue here to add some logic around the sudo call:

http://projects.theforeman.org/issues/3150

Actions #3

Updated by Dominic Cleal over 10 years ago

  • Related to Feature #3150: foreman-proxy support for invoking sudo as a different user for mcollective added
Actions #4

Updated by Ewoud Kohl van Wijngaarden almost 3 years ago

  • Status changed from New to Rejected

In #30429 puppetrun support was removed.

Actions

Also available in: Atom PDF