Bug 429116 - Configuration files being truncated in satellite
Summary: Configuration files being truncated in satellite
Status: CLOSED DUPLICATE of bug 427569
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Configuration Management
Version: 501
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Partha Aji
QA Contact: Steve Salevan
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-01-17 14:09 UTC by Nick Strugnell
Modified: 2009-02-19 16:19 UTC (History)
2 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2009-02-19 08:29:37 UTC


Attachments (Terms of Use)

Description Nick Strugnell 2008-01-17 14:09:34 UTC
Description of problem:
When using the WebUI to edit configuration files, the entered configuration file
is truncated.

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

How reproducible:
Intermittent

Steps to Reproduce:
1.Create a configuration channel
2.From the Channel Overview screen, select 'Add Files'
3.On the 'Add Files' submenu, select 'Create file'
4.On the next screen, type a file name and then some file contents in the large
textarea
5. Click the 'Create Configuration File' button

  
Actual results:
The saved file occasionally has the last few characters truncated. For example,
in one of our config files we have:

chage -d 0 root

as the last line.

This is always truncated to:

chage -d 0 r

Expected results:
No truncation should occur

Additional info:
There is no proxy in this configuration and the browser is running on the
satellite itself.

This is happening with short files (<1K)

Workaround is to add a comment as the last line of the file if possible as it
does not matter if this is truncated.

Comment 1 Nick Strugnell 2008-01-17 14:29:14 UTC
OK, the culprit is the following line in the configuration file:

/usr/sbin/usermod -p '$1$yñ1üµßIA$2HQp.OK2aS9lMt20ApKKI/' linux

Without this line, we don't see any truncation.




Comment 2 Michael Mayer 2008-01-31 12:33:30 UTC
That for sure is BZ#427569. The problem comes about by the use of UTF8
Characters in Configuration Files. This apparently was not foreseen in Satellite
5, but has been fixes in http://seg.rdu.redhat.com/scripts/hotfix/edit.pl?id=2489

Cheers,

Michael.

Comment 4 Nick Strugnell 2009-02-19 08:05:12 UTC
Its definitely Bug 427569 - can close as a duplicate.

Comment 5 Jose Plans 2009-02-19 08:29:37 UTC

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


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