Description of problem:
On Pod lists page, there is overlap between Node and Status column, reproduce on beremetal env and only normal user reproduces this issue.
Version-Release number of selected component (if applicable):
console image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:e6b3e376fd5e0e69d65d12f75e349691e21b155b196618dcbfc3cd9865c343cf
console commit: https://github.com/openshift/console/commit/d8fc460a3d0e9f8de3d14373de8f36ba09103537
Always on baremetal env
Steps to Reproduce:
1. Create applications and goes to Workloads -> Pods page
1. All pods are listed in the table with Node and Status column.
1. Node and Status data should be shown correctly
On the clusters setup on AWS, the issue is not reproduced although node such as `ip-10-0-153-65.us-east-2.compute.internal` has the same length with baremetal node name such as `dell-r730-067.dsal.lab.eng.rdu2.redhat.com`
Only normal user reproduces this issue and I guess that it should be format issue after disabling node link for normal user
Created attachment 1572352 [details]
Created attachment 1572353 [details]
Created attachment 1572354 [details]
Created attachment 1584639 [details]
console commit: 585dfbf26db35b5d566a20228fbe071de78b9f22
Checked on ocp 4.2 env with above version, the bug still could be reproduced on baremetal env by normal user.
Don't have a cluster with long node name, will check when there's
Normal user don't see this issue when node name is 41 chars long
Will continue to track the issue on other type of clusters
Verified on 4.3.0-0.nightly-2019-11-17-224250
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, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.