Bug 461500 - Unable to save kickstart using SCP
Unable to save kickstart using SCP
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-08 12:12 EDT by James Laska
Modified: 2013-09-02 02:27 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-09-08 13:11:30 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Screenshot.png (76.62 KB, image/png)
2008-09-08 12:12 EDT, James Laska
no flags Details
anacdump.txt (95.26 KB, text/plain)
2008-09-08 12:14 EDT, James Laska
no flags Details

  None (edit)
Description James Laska 2008-09-08 12:12:36 EDT
Created attachment 316098 [details]
Screenshot.png

Description of problem:

Unable to save traceback using SCP method.

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

anaconda-11.4.1.32-1.i386

$ /usr/sbin/snake-tree info
http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os/ 
No data source used
Name         : Fedora development i386 (20080908)
Arch         : i386
Id           : 1220873581.13
Version      : development
Family       : Fedora
Variant      : 
Time         : 2008-09-08 07:33 EDT
URI's        : 
Images       : i386 (kernel, initrd, boot.iso), xen (kernel, initrd)

How reproducible:
100%

Steps to Reproduce:
1. Boot into vmlinuz+initrd.img from
http://download.fedora.redhat.com/pub/fedora/linux/development/i386/os
2. Append updates=http://jlaska.fedorapeople.org/traceback.img
3. When traceback dialog presenting, click Save
4. Enter user, passwd, host, filename

Actual results:
There was a problem writing the system state to the remote host.

Expected results:
anacdump saved on remote host


Additional info:

See screenshot

 * I don't see any additional output written to tty[1-5] when this error message occurs.  
 * I'll attach the anacdump.txt that was used ot trigger the problem, but this will only indicate the expected traceback.
Comment 1 James Laska 2008-09-08 12:14:03 EDT
Created attachment 316099 [details]
anacdump.txt

Attaching expected anacdump.txt file that was manually transferred from tty2 using the `scp` command.  Note, this file represents an expected traceback ... I'm just attaching in the event that there is some additional logging data that might help triage.
Comment 2 Chris Lumens 2008-09-08 13:11:30 EDT
This will be fixed in the next build of anaconda.

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