Bug 1787587

Summary:	/etc/passwd misconfigured in ansible-operator base image
Product:	OpenShift Container Platform	Reporter:	Fabian von Feilitzsch <fabian>
Component:	Operator SDK	Assignee:	Joe Lanford <jlanford>
Status:	CLOSED ERRATA	QA Contact:	Fan Jia <jfan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	4.3.0	CC:	aos-bugs, eparis, jfan, jlanford, vlaad
Target Milestone:	---
Target Release:	4.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1787445	Environment:
Last Closed:	2020-01-23 11:19:28 UTC	Type:	---
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:
Bug Blocks:	1787445

Description Fabian von Feilitzsch 2020-01-03 14:32:04 UTC

+++ This bug was initially created as a clone of Bug #1787445 +++

Description of problem:
/etc/passwd not properly configured on Ansible Operator base image

When we moved away from allowing CRI-O to handle builds, it looks like we didn't re-enable the user_setup script, which sets the permissions on /etc/passwd to prevent CRI-O from attempting to write to set it up.



Version-Release number of selected component (if applicable):
4.4

How reproducible:
100%

Steps to Reproduce:
1. Start any Ansible-based operator

Actual results:
It crashes do to permissions errors

Expected results:
It starts successfully

Comment 1 Fabian von Feilitzsch 2020-01-03 20:34:32 UTC

There are no PR changes associated with this BZ, this was simply filed so that we can verify Ansible-based operators successfully start in 4.3, which will unblock the actual bug that is present in 4.2

Comment 3 Fan Jia 2020-01-06 02:45:09 UTC

The Ansible-based operators successfully start in 4.3.

Comment 5 errata-xmlrpc 2020-01-23 11:19:28 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-2020:0062