Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 859984 - traceback when update.img is used
Summary: traceback when update.img is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: s390x
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Cantrell
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ZedoraTracker
TreeView+ depends on / blocked
 
Reported: 2012-09-24 14:41 UTC by Dan Horák
Modified: 2013-01-10 02:22 UTC (History)
3 users (show)

Fixed In Version: anaconda-18.15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-16 19:04:59 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Dan Horák 2012-09-24 14:41:04 UTC 
[dan@eagle ~]$ ssh install.bos.redhat.com
Warning: Permanently added 'devel6.s390.bos.redhat.com,10.16.104.69' (RSA) to the list of known hosts.
Starting installer, one moment...
Traceback (most recent call last):
  File "/sbin/anaconda", line 629, in <module>
    setupPythonUpdates()
  File "/sbin/anaconda", line 146, in setupPythonUpdates
    "/tmp/%s" % dirname)
OSError: [Errno 17] File exists
Connection to devel6.s390.bos.redhat.com closed.

the workaround was "rm /tmp/updates" in parallel session logged in as root

Version-Release number of selected component (if applicable):
anaconda-18.8-1.fc18
Comment 1 Jesse Keating 2012-09-24 21:32:09 UTC 
the bug here is actually that you're doing anaconda via ssh rather than using the anaconda that already started via tmux on x3270. We don't have this hand off working right, it's a work in progress.
Comment 2 Jesse Keating 2012-10-16 19:04:59 UTC 
this should now be working.  Please re-test.
Note You need to log in before you can comment on or make changes to this bug.