RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 969389 - anaconda-tb file present after installation - IOError: [Errno 5] Input/output error
Summary: anaconda-tb file present after installation - IOError: [Errno 5] Input/output...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Vratislav Podzimek
QA Contact: Release Test Team
URL:
Whiteboard:
: 1014971 (view as bug list)
Depends On:
Blocks: 782468
TreeView+ depends on / blocked
 
Reported: 2013-05-31 10:52 UTC by Richard Marko
Modified: 2016-02-01 02:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-12-03 13:05:11 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Comment 2 David Cantrell 2013-08-02 17:09:48 UTC
Traceback (most recent call first):
  File "/usr/lib64/python2.7/atexit.py", line 29, in _run_exitfuncs
    print >> sys.stderr, "Error in atexit._run_exitfuncs:"
IOError: [Errno 5] Input/output error



/usr/lib64/python2.7/atexit.py is owned by the python package, not anaconda.  Reassigning.

Comment 3 Bohuslav "Slavek" Kabrda 2013-08-08 10:34:28 UTC
I'm unable to reproduce this with current composes of rhel 7. Richard, can you still see this issue?

It's quite hard to judge from the traceback file, but:
1) David, the fact that python package owns that file doesn't really mean that the problem is in the package. Do you have any more reasons why to believe that error is in Python?
2) From my experience, this errno can be raised when you have parent Python process that spawns child processes via subprocess module, but then the parent process and its terminal are closed => child processes have no terminal to write to. If this is the case, the problem could be pretty much anywhere where anaconda spawns subprocesses...

Comment 4 David Shea 2013-10-04 13:18:25 UTC
*** Bug 1014971 has been marked as a duplicate of this bug. ***

Comment 5 David Shea 2013-10-04 13:20:41 UTC
In reply to the comment on bug 1014971, anaconda reboots the system during the atexit calls, so yes, the terminal has been closed. That's not a good reason for atexit failing.

Comment 6 Bohuslav "Slavek" Kabrda 2013-10-07 10:36:49 UTC
(In reply to David Shea from comment #5)
> In reply to the comment on bug 1014971, anaconda reboots the system during
> the atexit calls, so yes, the terminal has been closed. That's not a good
> reason for atexit failing.

Actually, it's a perfect reason to fail. Python can't check whether the terminal is open before every print. So I guess this is Anaconda's problem and should be reassigned back to Anaconda, do you agree?

Comment 7 Bohuslav "Slavek" Kabrda 2013-11-05 11:13:14 UTC
Reassigning to Anaconda. As noted in the previous comment, Python can't check whether the terminal is open before every print. This should be checked in Anaconda.

Comment 8 Vratislav Podzimek 2013-11-06 15:53:34 UTC
Is this bug still reproducible with any of the recent composes? And if so, how? I cannot find any way to do so.

Comment 9 Richard Marko 2013-12-03 13:05:11 UTC
No. If I'll encounter it again I'll reopen this bug.


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