Bug 1760758 - label with long value is overlapping another one
Summary: label with long value is overlapping another one
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Management Console
Version: 4.2.z
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: 4.3.z
Assignee: Andrew Pickering
QA Contact: Junqi Zhao
URL:
Whiteboard:
Depends On: 1800494 1818722 1837784
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-10-11 09:17 UTC by Junqi Zhao
Modified: 2020-05-20 01:08 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1800494 (view as bug list)
Environment:
Last Closed: 2020-05-20 01:08:04 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
overlapping (88.44 KB, image/png)
2019-10-11 09:17 UTC, Junqi Zhao
no flags Details
overlapping - "node_role_os_version_machine:cpu_capacity_cores:sum" (47.65 KB, image/png)
2019-11-29 07:09 UTC, Junqi Zhao
no flags Details

Description Junqi Zhao 2019-10-11 09:17:16 UTC
Created attachment 1624645 [details]
overlapping

Description of problem:
search kube_persistentvolumeclaim_info in Query Browser
see the picture, label persistentvolumeclaim is overlapping label pod, length for persistentvolumeclaim is 22


Version-Release number of selected component (if applicable):
4.2.0-rc.5
firefox 66.0.4 (64-bit)
Chrome	75.0.3770.90 (Official Build) (64-bit)

How reproducible:
label with long value

Steps to Reproduce:
1. See the description
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Junqi Zhao 2019-11-29 07:09:19 UTC
Created attachment 1640588 [details]
overlapping - "node_role_os_version_machine:cpu_capacity_cores:sum"

Comment 3 Steve Goodwin 2020-02-18 20:41:13 UTC
Upstream release in https://github.com/patternfly/patternfly-next/releases/tag/v2.60.0

Comment 4 Andrew Pickering 2020-05-18 03:00:13 UTC
Looks like the upstream fix was pulled in by https://github.com/openshift/console/pull/5078, so only included from 4.5.

Comment 5 Andrew Pickering 2020-05-20 01:08:04 UTC
Actually, the upstream fix is available in 4.4, but not in 4.3, so not planning to back port fix to 4.3


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