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

common users are unable to create ephemeral/CSI volumes in upgraded clusters

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done-Errata
    • Icon: Critical Critical
    • 4.16.0
    • 4.13
    • apiserver-auth
    • Critical
    • No
    • False
    • Hide

      None

      Show
      None
    • Hide
      * Previously, `ephemeral` and `csi` volumes were not properly added to security context constraints (SCCs) on upgraded clusters. With this release, SCCs on upgraded clusters are properly updated to have `ephemeral` and `csi` volumes. (link:https://issues.redhat.com/browse/OCPBUGS-33522[*OCPBUGS-33522*])

      Show
      * Previously, `ephemeral` and `csi` volumes were not properly added to security context constraints (SCCs) on upgraded clusters. With this release, SCCs on upgraded clusters are properly updated to have `ephemeral` and `csi` volumes. (link: https://issues.redhat.com/browse/OCPBUGS-33522 [* OCPBUGS-33522 *])
    • Bug Fix
    • Done

      Description of problem:

          The storage team added CSI and ephemeral volumes in 4.12 and 4.13 but the affected SCCs are not being reconciled, resulting in these capabilities unreachable to the hands of the expected end users.

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

          4.13+

      How reproducible:

          100%

      Steps to Reproduce:

          1.check either of "anyuid", "hostaccess", "hostmount-anyuid", "hostnetwork", "nonroot", "restricted" SCCs on a cluster upgraded from 4.11

      Actual results:

          no "csi" and "ephemeral" in .volumes

      Expected results:

          "csi" and "ephemeral" in .volumes

      Additional info:

              slaznick@redhat.com Stanislav Láznička (Inactive)
              slaznick@redhat.com Stanislav Láznička (Inactive)
              Xingxing Xia Xingxing Xia
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: