Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 968715

Summary:	old_value and new_value column length too short for distro tree activity
Product:	[Retired] Beaker	Reporter:	Raymond Mancy <rmancy>
Component:	scheduler	Assignee:	beaker-dev-list
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.12	CC:	abenoit, qwan, tools-bugs
Target Milestone:	---	Keywords:	Triaged, UserExperience
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-10-21 14:13:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Raymond Mancy 2013-05-30 00:23:27 UTC

Description of problem:

It's impossible to get a meaningful view of distro tree activity
entries because the column is truncated to 60 chars.


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

0.12

How reproducible:

Always

Steps to Reproduce:
1. Import a distro tree
2.
3.

Actual results:

The tree urls are not fully displayed in the activity log
as they are almost always longer than 60 chars

Expected results:

Be able to see the complete URL

Additional info:

Comment 2 Dan Callaghan 2014-07-09 02:07:17 UTC

The other case where this is a problem is power script failure messages. Those are also typically multiple lines which is not handled by the current UI.

Comment 4 Dan Callaghan 2015-01-19 00:37:39 UTC

*** Bug 1183144 has been marked as a duplicate of this bug. ***

Comment 5 Dan Callaghan 2016-09-05 01:32:12 UTC

For the power commands specifically, this will be fixed by just divorcing the command_queue table from the activity tables entirely: bug 1318524. Therefore this issue with the length of old_value and new_value no longer applies there.

Converting the bug back to just being about distro tree activity, which still suffers this problem.