Bug 1877595 - serverless Service reason consumes a lot of vertical space
Summary: serverless Service reason consumes a lot of vertical space
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Dev Console
Version: 4.5
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.6.0
Assignee: Aritra Roy
QA Contact: Jaivardhan Kumar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-09 23:27 UTC by Aritra Roy
Modified: 2020-10-27 16:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-27 16:39:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 6560 0 None closed Bug 1877595: fix height for reason column of knative service table 2020-09-22 20:04:32 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:39:48 UTC

Description Aritra Roy 2020-09-09 23:27:44 UTC
Description of problem:
The reason text of a Service can be very large. As a result it makes browsing the list of Services very difficult.

Version-Release number of selected component (if applicable):
4.6.0-0.nightly-2020-08-02-091622

How reproducible:
always

Steps to Reproduce:
1.create a knative service
2.go to the service table
3.

Actual results:
the reason text can be large and consume lot of vertical space

Expected results:
the reason text should be limited to 5 lines and show full message on popover

Additional info:

Comment 2 Jaivardhan Kumar 2020-09-23 08:45:43 UTC
Verified on Version: 4.6.0-0.nightly-2020-09-22-213802

Comment 5 errata-xmlrpc 2020-10-27 16:39:32 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4196


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