Bug 1474339 - [3.5] Installer doesn't always use absolute path for excluders
Summary: [3.5] Installer doesn't always use absolute path for excluders
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.5.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: 3.5.z
Assignee: Jan Chaloupka
QA Contact: liujia
URL:
Whiteboard:
Depends On: 1474246 1474341
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-24 12:26 UTC by Scott Dodson
Modified: 2017-09-05 17:42 UTC (History)
5 users (show)

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.
Clone Of: 1474246
Environment:
Last Closed: 2017-09-05 17:42:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:2639 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-09-05 21:42:36 UTC

Comment 3 liujia 2017-08-21 02:28:01 UTC 
Bug can not be re-produced, still discussing with dev and reporter.
Comment 4 liujia 2017-08-21 10:40:48 UTC 
Bug has been reproduced, but no puddle available, assign bug back.
Comment 5 Scott Dodson 2017-08-22 20:02:45 UTC 
New puddle built with openshift-ansible-3.5.118-1
Comment 6 liujia 2017-08-23 05:07:30 UTC 
Version:
atomic-openshift-utils-3.5.118-1.git.0.cac343b.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
Note You need to log in before you can comment on or make changes to this bug.