Bug 817372

Summary: Spacecmd configchannel_addfile displays the base64 encoded file on the screen
Product: [Community] Spacewalk Reporter: Trent Johnson <rhbugzilla>
Component: ServerAssignee: Steven Hardy <shardy>
Status: CLOSED CURRENTRELEASE QA Contact: Red Hat Satellite QA List <satqe-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 1.8   
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-11-01 16:19:53 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:
Bug Depends On:    
Bug Blocks: 871344    

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