Description of problem: If a configuration file is uploaded through spacecmd, it is interpreted as binary. When changing it to text in the webui, and submitting this change. It will be reset to binary straight away. Version-Release number of selected component (if applicable): 1.8 How reproducible: Upload a text file through spacecmd Attempt to change to 'text' in the webui for the configuration file, assuming it is noted as 'binary' Expected results: File should be 'text' when changed from 'binary'
A workaround for this issue is to change anything else (like the file permissions for example) about the file when you try to updated and set the file to 'text'. The update will then take, and you can then set the file permissions (or whatever) back the way it was before.
Except when I do that it zeros out the content. :( Don't try the workaround in comment 1 yet.
The "zeroing out the data" bug has been filed as bug 1014800. I think there's a good bit of re-architecting that needs to be done to make this all work right.
Correction to this: Expectation is that the file should be interpreted correctly as text when uploaded, and it should not require an additional step (even if that step at the moment doesn't work).
This is now fixed with the following commits: 48248b7818e8b09bf25c6407c1d285baa1cca857 6daf599d669ec8b2f835991f0e30ac341e7f1d41 and in the following spacecmd build: spacecmd-2.1.25-1
Spacewalk 2.2 has been released: https://fedorahosted.org/spacewalk/wiki/ReleaseNotes22