Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 451644[details]
screenshot of exception
Description of problem:
anaconda shows an exception with stack trace
Version-Release number of selected component (if applicable):
13.21.82
OSError: [Errno 17] File exists: '/mnt/sysimage/root/DD-0'
anaconda 13.21.82 exception report
Traceback (most recent call first):
File "/usr/lib64/python2.6/os.py", line 157, in makedirs
mkdir(name, mode)
File "/usr/lib64/python2.6/shutil.py", line 146, in copytree
os.makedirs(dst)
File "/usr/lib/anaconda/backend.py", line 106, in doPostInstall
shutil.copytree(d, anaconda.rootPath + "/root/" + os.path.basename(d))
File "/usr/lib/anaconda/yuminstall.py", line 1831, in doPostInstall
AnacondaBackend.doPostInstall(self, anaconda)
File "/usr/lib/anaconda/backend.py", line 299, in doPostInstall
anaconda.backend.doPostInstall(anaconda)
File "/usr/lib/anaconda/dispatch.py", line 208, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 126, in gotoNext
self.moveStep()
File "/usr/lib/anaconda/gui.py", line 1338, in nextClicked
self.anaconda.dispatch.gotoNext()
File "/usr/lib/anaconda/iw/progress_gui.py", line 79, in renderCallback
self.intf.icw.nextClicked()
File "/usr/lib/anaconda/gui.py", line 1359, in handleRenderCallback
self.currentWindow.renderCallback()
OSError: [Errno 17] File exists: '/mnt/sysimage/root/DD-0'
How reproducible: always
Steps to Reproduce:
1. PXE installation with parameters "dd=http://.../megasr-13.21.0614.2010-8-001.iso blacklist=ahci"
Actual results:
See above
Expected results:
No exception
Additional info:
The file exists indeed (has probably been copied earlier already) AFAICS, the installation had been completed successfully.
I just found this was a user error (I didn't check the "format" check box when I chose a partition for RHEL installation, and that installation had already seen a previous RHEL installation). If I choose "format", the problem doesn't occur.
Sorry about this. However I may not be the only one who falls into this trap. Also, there were no problems with rpm file replacement etc., so anaconda seems to be prepared to an existing partition. Just the DD is causing trouble.
Created attachment 451647[details]
anaconda trace back
So the file did actually already exist before (from a previous RHEL6 installation with the same DD).
We have similar problem with rpm database on non-formated / partition and the "policy" was not touching existing data.
This shouldn't throw exception though as it is not essential file/dir.
Comment 6RHEL Program Management
2010-10-29 21:30:23 UTC
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux maintenance release. Product Management has
requested further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update release.
Comment 7Alexander Todorov
2010-12-01 21:55:22 UTC
qa_ack+
How to reproduce:
1) Install a system using a driver disk
2) Install the system again with the same driver disk
3) Select the previous root partition for the new installation but do NOT format it.
No exception/traceback should appear.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
http://rhn.redhat.com/errata/RHBA-2011-0530.html