[JCLOUDS-973] Sudo configuration for Suse Enterprise which prevents execution of superuser commands

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.9.0, 2.0.0
• Fix Version/s: 2.0.0
• Component/s: jclouds-compute, jclouds-scriptbuilder
• Environment: Suse Enterprise Linux 11 SP3 on AWS
• Assignee: Unassigned
• Reporter: Yavor Yanchev
• Created: 27/Jul/15 17:28
• Updated: 16/Oct/15 09:50
• Resolved: 31/Aug/15 23:16

Description

Some older Suse versions have a configuration which prevents provisioning of VMs with jclouds.
One such version is Suse Enterprise Linux 11. Its default PATH configuration for ordinary users is missing privileged paths such as /usr/sbin and /sbin.
The problem is explained with more details at: https://features.opensuse.org/310406

Current configuration for sudo created by jclouds

# cat /etc/sudoers
root ALL = (ALL) ALL
%wheel ALL = (ALL) NOPASSWD:ALL

It needs superuser paths to be part of the default user PATH configuration. This is the case for RedHat- and Debian-derivatives, but not for SLES 11

If jclouds' configuration for sudo is extended with the following the parameters:

Defaults    env_reset
Defaults    secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"

So it creates /etc/sudoers like:

Defaults    env_reset
Defaults    secure_path="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
root ALL = (ALL) ALL
%wheel ALL = (ALL) NOPASSWD:ALL

It will retain full backward compatibility and provide workaround for Suse deployments where sudo is needed and/or used.

Adding the parameters will not change the current behavior. It will just make it more explicit, because
1. By default, the env_reset option is enabled
2. secure_path parameter is already used by most of the Linux distributions