Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-76340

After upgrade to 4.20.10, ironic-proxy pods are in CrashLoopBackOff due to read-only file system

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None
    • 2
    • None
    • None
    • None
    • None
    • Metal Platform 284
    • 1
    • In Progress
    • Bug Fix
    • Hide
      Before this update, the Security Context Constraints (SCC) additionally set `readOnlyRootFilesystem: true`. As a consequence, read-only file system errors occurred. With this release, by default, SSC sets the `readOnlyRootFilesystem` value to false. As a result, read-only file system errors do not occur.
      Show
      Before this update, the Security Context Constraints (SCC) additionally set `readOnlyRootFilesystem: true`. As a consequence, read-only file system errors occurred. With this release, by default, SSC sets the `readOnlyRootFilesystem` value to false. As a result, read-only file system errors do not occur.
    • None
    • None
    • None
    • None

      Description of problem:

          After upgrade to 4.20.10, ironic-proxy pods are in CrashLoopBackOff with this error in the message output of the pod:

...
couldn't open temporary file /etc/httpd/conf/sedt26Dda: Read-only file system\n"

      How reproducible:

          Upgrade to 4.20.10 and see that the ironic-proxy pods receive the error above

      Additional info:

          Bug OCPBUGS-65971 appears to be exactly the same but that one is for the metal3-image-customization component. Probably a workaround similar to that one is possible.

              hroy@redhat.com Himanshu Roy
              rhn-support-msecaur Matthew Secaur
              Jad Haj Yahya Jad Haj Yahya
              None
              Votes:
              2 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: