Logging Playbook fails when changing the default permissions set on the tmpfs filesystems

Solution Unverified - Updated -

Issue

  • Installation of logging will fail if noexec is set on the mount point.
  • noexec option will not permit to execute any binaries directly on the mounted filesystem.
  • The logging playbook will fail at executing the binary as mentioned in the following logs:

    TASK [openshift_logging : Run JKS generation script] 
    <localhost> EXEC /bin/sh -c 'rm -f -r /home/ocpadmin/.ansible/tmp/ansible-tmp-1554024314.79-142933925028261/ > /dev/null 2>&1 && sleep 0'
    fatal: [master1.example.com -> localhost]: FAILED! => {
    "changed": true, 
    "msg": "non-zero return code", 
    "rc": 126, 
    "stderr": "/bin/sh: /home/admin/.ansible/tmp/ansible-tmp-1554024314.79-142933925028261/generate-jks.sh: Permission denied\n", 
    "stderr_lines": [
        "/bin/sh: /home/admin/.ansible/tmp/ansible-tmp-1554024314.79-142933925028261/generate-jks.sh: Permission denied"
    ], 
    "stdout": "", 
    "stdout_lines": []
    }
    

Environment

  • Red Hat OpenShift Container Platform
    • 3.11

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content