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.
Description of problem:
Anaconda throws a traceback when running installation using kickstart created during previous installation. Partitioning commands in the kickstart were uncommented except the line with the clearpart command:
#clearpart --all --drives=dasdb,dasdc,dasdd,dasde,dasdf,dasdg,dasdh,dasdi,dasdj,dasdk
ignoredisk --only-use=dasdi,dasdh,dasdk,dasdj,dasde,dasdd,dasdg,dasdf,dasdc,dasdb
part pv.094005 --grow --size=1
part pv.094009 --grow --size=1
part pv.094013 --grow --size=1
part pv.094017 --grow --size=1
part pv.094021 --grow --size=1
part pv.094025 --grow --size=1
part pv.094029 --grow --size=1
part pv.094033 --grow --size=1
part pv.094037 --grow --size=1
part pv.094041 --grow --size=1
volgroup vg_rtt6 --pesize=4096 pv.094005 pv.094009 pv.094013 pv.094017 pv.094021 pv.094025 pv.094029 pv.094033 pv.094037 pv.094041
logvol /boot --fstype=ext4 --name=lv_boot --vgname=vg_rtt6 --size=500
logvol / --fstype=ext4 --name=lv_root --vgname=vg_rtt6 --grow --size=1024 --maxsize=51200
logvol swap --name=lv_swap --vgname=vg_rtt6 --grow --size=752 --maxsize=1504
anaconda 13.21.107 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/__init__.py", line 766, in newVG
raise ValueError("name already in use")
File "/usr/lib/anaconda/kickstart.py", line 1066, in execute
peSize=self.pesize/1024.0)
File "/usr/lib/anaconda/kickstart.py", line 1180, in execute
obj.execute(self.anaconda)
File "/usr/bin/anaconda", line 1103, in <module>
ksdata.execute()
ValueError: name already in use
Version-Release number of selected component (if applicable):
RHEL6.1-20110323.1
anaconda-13.21.107-1.el6
How reproducible:
always
Steps to Reproduce:
1. install RHEL6.1, use autopartitiong
2. copy /root/anaconda_ks.cfg from the system and uncomment all partitioning commands except the clearpart command
3. start new installation using the modified kickstart
Actual results:
traceback during the installation
Expected results:
no traceback, human-readable error message is displayed instead
Comment 7Alexander Todorov
2011-08-11 16:02:27 UTC
Created attachment 517833[details]
error dialog (as expected)
Reproduced on 6.1 KVM guest, tested with anaconda-13.21.126 on 6.2 nightly and got an error dialog telling that the specified volume group name is already in use. See screenshot.
Comment 9Red Hat Case Diagnostics
2011-10-08 02:25:11 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1565.html
Description of problem: Anaconda throws a traceback when running installation using kickstart created during previous installation. Partitioning commands in the kickstart were uncommented except the line with the clearpart command: #clearpart --all --drives=dasdb,dasdc,dasdd,dasde,dasdf,dasdg,dasdh,dasdi,dasdj,dasdk ignoredisk --only-use=dasdi,dasdh,dasdk,dasdj,dasde,dasdd,dasdg,dasdf,dasdc,dasdb part pv.094005 --grow --size=1 part pv.094009 --grow --size=1 part pv.094013 --grow --size=1 part pv.094017 --grow --size=1 part pv.094021 --grow --size=1 part pv.094025 --grow --size=1 part pv.094029 --grow --size=1 part pv.094033 --grow --size=1 part pv.094037 --grow --size=1 part pv.094041 --grow --size=1 volgroup vg_rtt6 --pesize=4096 pv.094005 pv.094009 pv.094013 pv.094017 pv.094021 pv.094025 pv.094029 pv.094033 pv.094037 pv.094041 logvol /boot --fstype=ext4 --name=lv_boot --vgname=vg_rtt6 --size=500 logvol / --fstype=ext4 --name=lv_root --vgname=vg_rtt6 --grow --size=1024 --maxsize=51200 logvol swap --name=lv_swap --vgname=vg_rtt6 --grow --size=752 --maxsize=1504 anaconda 13.21.107 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/__init__.py", line 766, in newVG raise ValueError("name already in use") File "/usr/lib/anaconda/kickstart.py", line 1066, in execute peSize=self.pesize/1024.0) File "/usr/lib/anaconda/kickstart.py", line 1180, in execute obj.execute(self.anaconda) File "/usr/bin/anaconda", line 1103, in <module> ksdata.execute() ValueError: name already in use Version-Release number of selected component (if applicable): RHEL6.1-20110323.1 anaconda-13.21.107-1.el6 How reproducible: always Steps to Reproduce: 1. install RHEL6.1, use autopartitiong 2. copy /root/anaconda_ks.cfg from the system and uncomment all partitioning commands except the clearpart command 3. start new installation using the modified kickstart Actual results: traceback during the installation Expected results: no traceback, human-readable error message is displayed instead