Bug 796899

Summary:	when saving traceback to remote system, name defaults to "tmp" instead of original file name
Product:	[Fedora] Fedora	Reporter:	Andre Robatino <robatino>
Component:	report	Assignee:	Gavin Romig-Koch <gavin>
Status:	CLOSED WONTFIX	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	17	CC:	awilliam, gavin, g.kaviyarasu, jmoskovc, jonathan, vanmeeuwen+fedora
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	RejectedNTH
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-08-01 00:27:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Andre Robatino 2012-02-23 20:12:53 UTC

Description of problem:
Running the test

https://fedoraproject.org/wiki/QA:Testcase_Anaconda_save_traceback_to_remote_system

I found that if you don't specify the file name on the remote system, instead of defaulting to the original name (like abrt-upload-2012-02-23-19:56:43-583.tar.gz), it just uses "tmp", which is easy to overlook. I originally thought it wasn't writing the file at all. Can it use the original name instead?

Version-Release number of selected component (if applicable):
whatever is in 17 Alpha Gold (AKA RC4), I think anaconda 17.11?

Comment 1 Adam Williamson 2012-03-26 15:17:53 UTC

Proposing as NTH (doesn't really violate criteria but is an obvious candidate to get fixed and can't be done with updates).



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 2 Adam Williamson 2012-03-30 19:32:11 UTC

Discussed at 2012-03-30 NTH review meeting. Rejected as NTH, because the workaround isn't too bad, and we're worried about poking libreport at this stage.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 3 Adam Williamson 2012-04-06 05:19:18 UTC


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 4 Fedora End Of Life 2013-07-03 22:30:21 UTC

This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2013-08-01 00:28:03 UTC

Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.