Description of problem:
Today we can't queue vmcores if a space is in the name. This is a special case and probably low priority but it would be good if it can be handled, or there is some workaround.
Version-Release number of selected component (if applicable):
Probably every time but unsure.
Steps to Reproduce:
1. Upload a vmcore to ftp site with a space in the name. Example: "
Trying to queue it from 'manager' gives "There is no such task"
Able to queue the vmcore from the 'manager' page same as other vmcores.
I tried to use "%20" added to the URL but got the same result.
I can provide a example in our local system.
*** Bug 1025123 has been marked as a duplicate of this bug. ***
Fixed in upstream
Author: Michal Toman <firstname.lastname@example.org>
Date: Wed Feb 26 16:12:32 2014 +0100
use urllib.quote() instead of urllib.quote_plus()
the '+' gets double quoted when used within <a> tag, while '%20' does not
Signed-off-by: Michal Toman <email@example.com>
retrace-server-1.11-1.el6 has been submitted as an update for Fedora EPEL 6.
* should fix your issue,
* was pushed to the Fedora EPEL 6 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=epel-testing retrace-server-1.11-1.el6'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
Looks fixed to me. I did not upload a vmcore though to the ftp site and try that method. Submitting a vmcore 'vmcore with spaces' via 'custom core location' worked though. I did not need to quote the file - just provide the full path with spaces included.
retrace-server-1.12-2.el6 has been submitted as an update for Fedora EPEL 6.
retrace-server-1.12-2.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.