Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.19.0, 4.20.0
Component/s: Management Console
Labels:
None

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

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None

Target Backport Versions:
None
Target Version:

4.20.0
Release Blocker:
None
Sprint:
None

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

Release Note Status:
In Progress
Release Note Type:
Release Note Not Required
Release Note Text:
None

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

Description of problem:

    the rosa logo in managed-cluster-config is different to the one we have in console. this causes branding differences whether "rosa" branded cluster is launched vs. when an actual rosa cluster is launched

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

    4.20, 4.19, 4.18, 4.17, 4.16, ...

How reproducible:

    always

Steps to Reproduce:

    1. launch a rosa cluster via clusterbot
    2. launch console locally via bridge -branding rosa
    3.

Actual results:

    logos are different

Expected results:

    logos are the same

Additional info:

is duplicated by

OCPBUGS-55803 ROSA product name text lacks sufficient contrast in Light theme

Verified

links to

openshift/managed-cluster-config#2430: OCPBUGS-56264, OCPBUGS-55803: add legacy branding

Assignee:: Jackson Lee

Reporter:: Jackson Lee

Need Info From:: None

Contributors:: None

QA Contact:: YaDan Pei

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 5 Start watching this issue

Created:: 2025/05/15 4:47 PM

Updated:: 2025/07/13 1:12 PM

Resolved:: 2025/05/27 12:40 PM

Details

Description

Attachments

Issue Links

Easy Agile Planning Poker

Activity

People

Dates

Hide