Bug 2067155 - Incorrect operator display name shown in pipelines quickstart in devconsole
Summary: Incorrect operator display name shown in pipelines quickstart in devconsole
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.0
Assignee: Karthik Jeeyar
QA Contact: spathak@redhat.com
Depends On:
Blocks: 2078912
TreeView+ depends on / blocked
Reported: 2022-03-23 12:24 UTC by Pavol Pitonak
Modified: 2022-08-10 10:56 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-08-10 10:55:33 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift console-operator pull 650 0 None open Bug 2067155: Modify the operator display name to match it with the name displayed in operatorhub 2022-04-21 11:47:22 UTC
Red Hat Product Errata RHSA-2022:5069 0 None None None 2022-08-10 10:56:28 UTC

Description Pavol Pitonak 2022-03-23 12:24:13 UTC
Description of problem:

Second step of quickstart "Install the OpenShift Pipelines Operator"

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

4.10.5, probably also older releases

How reproducible:

Steps to Reproduce:
1. start quickstart "In the Filter by keyword field, type OpenShift Pipelines Operator."
2. perform steps 1 and 2

Actual results:

No operator is displayed so user cannot proceed with installation

Expected results:

All operators but "OpenShift Pipelines" are filtered out and user proceeds to step 3.

Additional info:

Comment 4 spathak@redhat.com 2022-05-08 10:38:33 UTC
Verified on build version: 4.11.0-0.nightly-2022-05-07-114518
Browser version: Chrome 99

Comment 6 errata-xmlrpc 2022-08-10 10:55:33 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 (Important: OpenShift Container Platform 4.11.0 bug fix and security 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.