Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1474341

Summary: [3.4] Installer doesn't always use absolute path for excluders
Product: OpenShift Container Platform Reporter: Scott Dodson <sdodson>
Component: InstallerAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: liujia <jiajliu>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.4.1CC: aos-bugs, jialiu, jokerman, mmccomas, sjr
Target Milestone: ---   
Target Release: 3.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
If the ansible_ssh_user didn't have /sbin in their path then the playbooks may have failed to execute the excluder scripts during installation and upgrade. The full path is now used avoiding this problem.
Story Points: ---
Clone Of: 1474246 Environment:
Last Closed: 2017-09-05 17:42:58 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1474246    
Bug Blocks: 1474339    

Comment 1 Jan Chaloupka 2017-08-17 14:29:06 UTC
Upstream PR: https://github.com/openshift/openshift-ansible/pull/5116

Comment 3 liujia 2017-08-21 02:27:48 UTC
Bug can not be re-produced, still discussing with dev and reporter.

Comment 4 liujia 2017-08-21 10:40:08 UTC
Bug has been reproduced, but no puddle available, assign bug back.

Comment 5 Scott Dodson 2017-08-22 20:05:07 UTC
openshift-ansible-3.4.128-1 in the latest puddle

Comment 6 liujia 2017-08-23 03:21:14 UTC
Version:
atomic-openshift-utils-3.4.128-1.git.0.45b61cf.el7.noarch

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

Install succeed.

Comment 8 errata-xmlrpc 2017-09-05 17:42:58 UTC
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.

https://access.redhat.com/errata/RHBA-2017:2639