Loading...

XML

Word

Printable

Type: Bug
Resolution: Not a Bug
Priority: Critical
Fix Version/s: None
Affects Version/s: 4.20.0
Component/s: Multi-Arch / IBM P and Z
Labels:
None

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Important
Regression:
None
Architecture:

s390x

Target Backport Versions:
None
Target Version:
None
Release Blocker:
Proposed
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

   When logged in to the Openshift console as kubeadmin user, OperatorHub is not getting listed under the Ecosystem.

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

4.20.0-rc.0    4.20.0-rc.1

How reproducible:

    Always reproducible

Steps to Reproduce:

    1. Install OCP version 4.20.0-rc0 on IBM Z
    2. Access the OCP console, login as kubeadmin user
    3. Go to EcoSystem, and only Installed Operators and Software Catalog options are visible. Operator Hub is not listed.

Actual results:

    Only Installed Operators and Software Catalog options are visible under Ecosystem option in the console menu.

Expected results:

    Along with Installed Operators and Software Catalog, even Operator Hub option should be listed

Additional info:

    The Operator Hub option was visible in the UI in OCP with version 4.20.0-ec.6

Assignee:: Kha Do (Inactive)

Reporter:: Suman Jainkeri

Need Info From:: None

Contributors:: Dennis Periquet

QA Contact:: None

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2025/09/11 7:44 AM

Updated:: 2025/09/16 10:40 AM

Resolved:: 2025/09/16 10:39 AM