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

Pre-release testing of CRW 2.2.0

    XMLWordPrintable

Details

    • QE Task
    • Resolution: Done
    • Major
    • 2.2.0.GA
    • 2.2.0.GA
    • testing
    • None
    • QE-2020-06-23 (Sprint: 185), QE-2020-07-14 (Sprint: 186)

    Description

      We need to test CRW 2.2.0 release candidates according to CRW 2.2.0 Test Plan on OpenShift 4.4, 3.11, 4.5.
      In case of enough time & resources available, we will perform smoke tests on OCP 4.3.

      Attachments

        Issue Links

          is related to

          Bug - A problem that impairs or prevents the functions of the product. CRW-967 Installation of CRW with OS OAuth by crwctl with operator installer failed because operator was unable to get openshift oauth

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Bug - A problem that impairs or prevents the functions of the product. CRW-930 quay.io/crw/operator-rhel8:2.2-7 image failed to install CRW 2.2.0.RC0

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-933 RH SSO deployment had failed in quay.io/crw/operator-rhel8:2.2-8 due to invalid path to cacerts file

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-944 quay.io/crw/server-rhel8:2.2-4 failed to startup of application server

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-948 quay.io/crw/operator-metadata:2.2-14 contains incorrect SHA of quay.io/crw/devfileregistry-rhel8:2.2 image

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-957 Can't start new workspace because mkdir pod failed to start because of PVC binding timeout

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-958 Can't start workspace because admission webhook "mutate-ws-resources.che-workspace-controller.svc" denied the request: 'org.eclipse.che.workspace/creator' label is missing.

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          Bug - A problem that impairs or prevents the functions of the product. CRW-949 Cannot start workspace from java devfiles

          • Critical - To be worked on immediately following BLOCKER issues.
          • Closed

          QE Task - QE Task CRW-945 initStacksTest.sh failed after switching to Eclipse Che 7.14.x typescript selenium tests codebase

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          QE Task - QE Task CRW-929 Adapt CRW 2.x testing pipelines to test CRW 2.2.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-940 Cleanup java selenium tests for CRW 2.2.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-946 E2E user story test pipeline doesn't fail after initStacksTest.sh failed

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-947 com.redhat.codeready.selenium.ocpoauth.** E2E tests failed on CRW 2.2.0.RC0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed
          relates to

          Bug - A problem that impairs or prevents the functions of the product. CRW-961 quay.io/crw/pluginregistry-rhel8:2.2-137 references to registry.redhat.io

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Closed

          QE Task - QE Task CRW-937 Align E2E user stories tests to CRW 2.2.0 workspace devfiles

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-953 Update E2E automated tests to check migration from CRW 2.1.1 to 2.2.0 by using OperatorHub

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          QE Task - QE Task CRW-1020 Update Jenkins pipelines which check installation of CRW in https mode using OperatorHub with external RH SSO / Postgres

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Closed

          Activity

            People

              dnochevn Dmytro Nochevnov
              dnochevn Dmytro Nochevnov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: