Bug 606982 - configchannel.createOrUpdatePath doesn't allow creation of binary files
Summary: configchannel.createOrUpdatePath doesn't allow creation of binary files
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: API (Show other bugs)
(Show other bugs)
Version: 530
Hardware: x86_64 Linux
low
medium
Target Milestone: ---
Assignee: Tomas Lestach
QA Contact: Red Hat Satellite QA List
URL:
Whiteboard:
Keywords:
Depends On:
Blocks: 462714
TreeView+ depends on / blocked
 
Reported: 2010-06-22 20:38 UTC by Aron Parsons
Modified: 2016-01-04 05:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-07-19 20:12:48 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Aron Parsons 2010-06-22 20:38:03 UTC
Description of problem:
configchannel.createOrUpdatePath doesn't allow creation of binary files.  It allows you to pass a base64 encoded string, but doesn't mark it as binary.  The file is stored as a text file with the contents being the base64 encoded string.

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

How reproducible:
Always

Steps to Reproduce:
1. in Python: contents = open('/bin/sleep', 'rb').read().encode('base64')
2. set the 'contents' in the data structure and call configchannel.createOrUpdatePath()
  
Actual results:
Satellite doesn't recognize base64 encoded contents and marks the file as text in the configuration channel

Expected results:
Satellite should notice the base64 encoded string and mark the file as binary in the configuration channel

Additional info:


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