Uploaded image for project: 'Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces) '
  1. Red Hat OpenShift Dev Spaces (formerly CodeReady Workspaces)
  2. CRW-3554

Dashboard ignores "disableContainerBuildCapabilities: true" CheCluster property when there is "openShiftSecurityContextConstraint: container-build"

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Hide
      = Workspaces failed to start with a clone of a Git repository on some {prod-short} instances

      Before this update, there was a regression in the {prod-short} instances that had been installed through the OpenShift web console. {prod-short} failed to link:https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.3/html-single/user_guide/index#starting-a-new-workspace-with-a-clone-of-a-git-repository[start workspaces with a clone of a Git repository], displaying an Operator permission error. With this update, this issue is resolved, and users on the affected {prod-short} instances can start new workspaces by supplying the URL of a remote Git repository.
      Show
      = Workspaces failed to start with a clone of a Git repository on some {prod-short} instances Before this update, there was a regression in the {prod-short} instances that had been installed through the OpenShift web console. {prod-short} failed to link: https://access.redhat.com/documentation/en-us/red_hat_openshift_dev_spaces/3.3/html-single/user_guide/index#starting-a-new-workspace-with-a-clone-of-a-git-repository [start workspaces with a clone of a Git repository], displaying an Operator permission error. With this update, this issue is resolved, and users on the affected {prod-short} instances can start new workspaces by supplying the URL of a remote Git repository.
    • Bug Fix
    • Rejected

      Description of problem:

      There were 2 problems:

      • Dashboard ignores "disableContainerBuildCapabilities: true" CheCluster property when there is "openShiftSecurityContextConstraint: container-build"
      • devspaces operator didn't remove "openShiftSecurityContextConstraint: container-build" property when restore "disableContainerBuildCapabilities: true" in CheCluster manually.

      As a result, it was not possible to start any workspace because of error: "operator does not have permissions to get the 'container-build' SecurityContextConstraints"

      Prerequisites (if any, like setup, operators/versions):

      • DWO 0.17.0: 'registry-proxy.engineering.redhat.com/rh-osbs/devworkspace-operator-bundle:0.17-1, registry-proxy.engineering.redhat.com/rh-osbs/iib:360655'
      • DS 3.3.0.ER-11-16: 'devspaces-operator-bundle:3.3-231'

      Steps to Reproduce

      1. Deploy DevSpaces with "disableContainerBuildCapabilities: false"
      2. Wait on DevSpaces being deployed completely
      3. Go to CheCluster and restore "disableContainerBuildCapabilities: true"

      Actual results:

      There was next un-removed property in CheCluster:

        devEnvironments:
    containerBuildConfiguration:
      openShiftSecurityContextConstraint: container-build

      As result, workspace failed to start because of error "operator does not have permissions to get the 'container-build' SecurityContextConstraints":

      Expected results:

      There was no "openShiftSecurityContextConstraint: container-build" in CheCluster

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Additional info (Such as Logs, Screenshots, etc):

        1. Screenshot from 2022-11-23 02-56-20.png
          Screenshot from 2022-11-23 02-56-20.png
          59 kB

              rhn-support-olorel Oleksii Orel (Inactive)
              dnochevn Dmytro Nochevnov
              Jana Vrbkova Jana Vrbkova
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: