Bug 817372 - Spacecmd configchannel_addfile displays the base64 encoded file on the screen
Summary: Spacecmd configchannel_addfile displays the base64 encoded file on the screen
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Spacewalk
Classification: Community
Component: Server
Version: 1.8
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Steven Hardy
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Depends On:
Blocks: space18
TreeView+ depends on / blocked
 
Reported: 2012-04-29 13:56 UTC by Trent Johnson
Modified: 2012-11-01 16:19 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-01 16:19:53 UTC
Embargoed:

Attachments (Terms of Use)

Description Trent Johnson 2012-04-29 13:56:05 UTC 
Description of problem:

When using configchannel_addfile in spacecmd, if a file has a trailing newline, it is base64 encoded, and then the base64 encoding is dumped to stdout.  Since base64 encoding is not useful to humans, it is just added noise on the screen for no reason.


How reproducible:
run spacemd configchannel_addfile /path/to/a/text/file.txt

  
Actual results:
You will see a bunch of base64 encoded noise on the terminal after the upload is complete.

Expected results:
The file is not displayed at all, or a text representation is displayed

Additional info:
Comment 1 Steven Hardy 2012-05-15 16:25:04 UTC 
Fixed by a2a351947e2721b5d23b08439e838df159fa2137

Please verify in next spacewalk-nightly spacecmd (1.8.6-1)
Comment 2 Jan Pazdziora 2012-10-30 19:24:32 UTC 
Moving ON_QA. Packages that address this bugzilla should now be available in yum repos at http://yum.spacewalkproject.org/nightly/
Comment 3 Jan Pazdziora 2012-11-01 16:19:53 UTC 
Spacewalk 1.8 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes18
Note You need to log in before you can comment on or make changes to this bug.