Bug 1889382 - Availability of codeReady Workspace operator in operatorhub 4.6 OCP
Summary: Availability of codeReady Workspace operator in operatorhub 4.6 OCP
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.6
Hardware: All
OS: All
Target Milestone: ---
: 4.6.z
Assignee: Karthik Jeeyar
QA Contact: Karthik Jeeyar
Depends On:
TreeView+ depends on / blocked
Reported: 2020-10-19 14:19 UTC by Karthik Jeeyar
Modified: 2020-11-09 15:51 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-09 15:50:59 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4339 0 None None None 2020-11-09 15:51:22 UTC

Description Karthik Jeeyar 2020-10-19 14:19:48 UTC
Description of problem:
The availability of codeReady Workspace features in ODC are dependent on the availability of the codeReady workspace operator. Currently this operator is not available on the fresh installation of OCP 4.6. However these features, are available when you upgrade OCP from a previous version to the latest.

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

How reproducible:

Steps to Reproduce:
1.Get a fresh 4.6 OCP cluster
2.Go to administrator ->  operatorHub
3. Search for codeReady workspace

Actual results:
No results found

Expected results:
Should be able to find the codeReady Workspace operator.

Additional info:

Comment 2 Karthik Jeeyar 2020-11-02 08:07:41 UTC
Verified on a fresh 4.6 cluster install, the CodeReady Workspace operator is available on the operatorhub.

Comment 5 errata-xmlrpc 2020-11-09 15:50:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (OpenShift Container Platform 4.6.3 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.