Bug 1324506 - Don't truncate template names on 32 characters
Summary: Don't truncate template names on 32 characters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Remote Execution
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium vote
Target Milestone: Unspecified
Assignee: Marek Hulan
QA Contact: Adam Ruzicka
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-06 13:46 UTC by Stephen Benjamin
Modified: 2019-09-25 20:34 UTC (History)
3 users (show)

Fixed In Version: rubygem-foreman_remote_execution-0.3.0.5-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-07-27 11:34:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 14496 0 None None None 2016-04-22 15:50:50 UTC

Description Stephen Benjamin 2016-04-06 13:46:14 UTC
Comment 1 Stephen Benjamin 2016-04-06 13:46:16 UTC 
Created from redmine issue http://projects.theforeman.org/issues/14496
Comment 2 Stephen Benjamin 2016-04-06 13:46:19 UTC 
Upstream bug assigned to mhulan
Comment 3 Stephen Benjamin 2016-04-06 13:51:23 UTC 
Verification steps:

1. Visit Host / Job Templates
2. Ensure the default template names aren't truncated too early (e.g. a large browser window you should see the full name)
Comment 5 Bryan Kearney 2016-04-06 14:03:00 UTC 
Moving to POST since upstream bug http://projects.theforeman.org/issues/14496 has been closed
-------------
Marek Hulán
Applied in changeset commit:foreman_plugin|ec3886088717bfa4453217250ccdca464b2fa978.
Comment 6 Adam Ruzicka 2016-05-30 07:32:24 UTC 
VERIFIED.

@Sat6.2.0-Snap13.1
tfm-rubygem-foreman_remote_execution-0.3.0.8-1.el7sat.noarch

Verified using steps described in comment #3:

Job template names are not truncated
Comment 7 Bryan Kearney 2016-07-27 11:34:15 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, 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-2016:1501
Note You need to log in before you can comment on or make changes to this bug.