Description of problem: When there is no rhn systemid and --name parameter was not used, hostname is used as a part of sosreport tarball name. sosreport should handle this hostname more carefully to handle wrong hostnames in a sane way. # hostname 'f/t_u-r:!§@#$%^>._ha_*()=+"`;/\?~|}{][hěščÁŤďh hh' # sosreport --batch -o general sosreport (version 2.2) This utility will collect some detailed information about the hardware and setup of your Red Hat Enterprise Linux system. The information is collected and an archive is packaged under /tmp, which you can send to a support representative. Red Hat Enterprise Linux will use this information for diagnostic purposes ONLY and it will be considered confidential information. This process may take a while to complete. No changes will be made to your system. Running plugins. Please wait ... Completed [1/1] ... /bin/sh: gt: command not found /bin/sh: -2012051614411337172088: command not found /bin/tar: t_u-r\:!§@#$%^: Cannot stat: No such file or directory /bin/tar: Exiting with failure status due to previous errors sh: gt: command not found sh: -2012051614411337172088: command not found Creating compressed archive... Your sosreport has been generated and saved in: /tmp/f/sosreport-ftu-rgt-20120516144129-e888.tar.xz The md5sum is: 8dc5aea5b03dff8595f096f9e368e888 Please send this file to your support representative. --- Version-Release number of selected component (if applicable): sos-2.2-27.el6.noarch How reproducible: Always Steps to Reproduce: 1. see above 2. 3. Actual results: Expected results: Additional info:
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
While I think we're unlikely to come across it very often this is potentially a bit nasty - weird characters in the hostname can cause us to go wandering off around the file system in strange ways. I've added a filter to the hostname to only accept alphanumeric, dots, dashes and underscores. That's more strict than it really needs to be but leaves less potential for trouble.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0474.html