Red Hat Bugzilla – Bug 1474246
[3.6] Installer doesn't always use absolute path for excluders
Last modified: 2017-09-05 13:42:58 EDT
Description of problem:
Version-Release number of the following components:
rpm -q openshift-ansible
rpm -q ansible
Steps to Reproduce:
1. PATH doesn't include '/sbin'
2. run the installer
3. installer will fail here:
Task "Enable docker excluder" fails as it doesn't use the excluder absolute path.
Use the absolute path for the excluder as in other tasks, e.g.:
master branch fix in https://github.com/openshift/openshift-ansible/pull/4839 and https://github.com/openshift/openshift-ansible/pull/4835
Upstream PR: https://github.com/openshift/openshift-ansible/pull/5117
3.6 backport as well: https://github.com/openshift/openshift-ansible/pull/5115
Have added cases ocp-15375 and ocp-15380 to cover this scenario.
1. Create a non-root user on the host.
2. Add cloud-user to sudo group and edit /etc/sudoers to change sudo's secure path(delete default /sbin and /usr/sbin):
Defaults secure_path = /bin:/usr/bin
3. Run install playbook with user cloud-user.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.