Bug 1302563

Summary: Docker container UUID truncated despite a LOT of free space on screen
Product: Red Hat Satellite Reporter: Pavel Moravec <pmoravec>
Component: Container ManagementAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: UnspecifiedCC: bbuckingham, bkearney
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-08 18:22:47 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:
Attachments:
Description Flags
screenshot none

Description Pavel Moravec 2016-01-28 08:04:49 UTC
Created attachment 1119047 [details]
screenshot

Description of problem:
Clicking to a docker container details, I can't get it's UUID since it is truncated - see attachment. The UUID is truncated despite I have PLENTY of free space all over the screen.

It is nice the UUID is displayed when I move mouse over it. But I can't copy the full UUID there - whenever I try to move mouse to the bubble with the full UUID (to mark the text there), it disappears (since I moved out from the shortened UUID).

Yes, I can inspect the element in my Firefox and copy it from there, but is that the user experience we want to have?


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


How reproducible:
100%


Steps to Reproduce:
1. Create a docker container
2. Open its details and check UUID


Actual results:
UUID is not complete, ends by ".."


Expected results:
full UUID written


Additional info:

Comment 2 Brad Buckingham 2016-07-08 18:22:47 UTC
Unfortunately, this is a common issue in some parts of the UI.  It is currently being tracked with bug 1160735; therefore, I am going to close this one as a duplicate.  The intent should be to have a generic solution to this issue.

*** This bug has been marked as a duplicate of bug 1160735 ***