Hide Forgot
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.2.z How reproducible: 100% Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This also blocks all tests for the 4.2 Ansible Operator base image.
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
test result: operator-sdk version: branch release 4.2 50b14bf4-dirty, commit: 50b14bf4705450bac99cc70730865c405be30567 generate one ansible operator "memcached" and run in 4.2 cluster success #oc get deployment NAME READY UP-TO-DATE AVAILABLE AGE memcached-operator 1/1 1 1 3m47s #oc get pods NAME READY STATUS RESTARTS AGE example-memcached-memcached-7db5f499d-c779w 1/1 Running 0 88s example-memcached-memcached-7db5f499d-djjvj 1/1 Running 0 88s example-memcached-memcached-7db5f499d-tbtxf 1/1 Running 0 88s memcached-operator-f78969fdd-74lsh 2/2 Running 0 2m34s
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:0107