Bug 691817 - ValueError: name already in use
Summary: ValueError: name already in use
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: anaconda
Version: 6.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: David Lehman
QA Contact: Release Test Team
URL:
Whiteboard:
: 726591 (view as bug list)
Depends On:
Blocks: 670159 705163
TreeView+ depends on / blocked
 
Reported: 2011-03-29 14:36 UTC by Jan Stodola
Modified: 2018-11-14 11:17 UTC (History)
2 users (show)

Fixed In Version: anaconda-13.21.125-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 10:31:06 UTC
Target Upstream Version:


Attachments (Terms of Use)
File: backtrace (234.51 KB, text/plain)
2011-07-31 00:09 UTC, Red Hat Case Diagnostics
no flags Details
error dialog (as expected) (111.61 KB, image/png)
2011-08-11 16:02 UTC, Alexander Todorov
no flags Details
File: backtrace (225.92 KB, text/plain)
2011-10-08 02:25 UTC, Red Hat Case Diagnostics
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1565 0 normal SHIPPED_LIVE anaconda bug fix and enhancement update 2011-12-06 00:39:12 UTC

Description Jan Stodola 2011-03-29 14:36:09 UTC
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 2 David Lehman 2011-07-29 17:41:39 UTC
*** Bug 726591 has been marked as a duplicate of this bug. ***

Comment 5 Red Hat Case Diagnostics 2011-07-31 00:09:18 UTC
Created attachment 515992 [details]
File: backtrace

Comment 7 Alexander 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 9 Red Hat Case Diagnostics 2011-10-08 02:25:11 UTC
Created attachment 526988 [details]
File: backtrace

Comment 11 errata-xmlrpc 2011-12-06 10:31:06 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


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