Bug 463843

Summary: AttributeError: 'NoneType' object has no attribute 'pesize'
Product: Red Hat Enterprise Linux 5 Reporter: Jeff Burke <jburke>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Brock Organ <borgan>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.3CC: ddumas, dzickus, lwang, pbunyan, rvykydal
Target Milestone: rcKeywords: TestBlocker
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-09-25 13:34:57 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Full failure from anaconda none

Description Jeff Burke 2008-09-24 20:59:50 UTC
Created attachment 317624 [details]
Full failure from anaconda

Description of problem:
While installing RHEL5.3-Server-20080919.1 I manually tried to change the size of the LVM volume. When I did that an exception occurred.

Version-Release number of selected component (if applicable):
RHEL5.3-Server-20080919.1

How reproducible:
Always

Steps to Reproduce:
1. Manually manipulate the default LVM Group  
  
Actual results:
Traceback (most recent call first):
  File "/usr/lib/anaconda/partRequests.py", line 981, in getActualSize
    retval = lvm.clampLVSizeRequest(retval, vgreq.pesize)
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 445, in editLogicalVolume
    sizeEntry.set_text("%Ld" % (logrequest.getActualSize(self.partitions, self.diskset),))
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 764, in addLogicalVolumeCB
    self.editLogicalVolume(request, isNew = 1)
AttributeError: 'NoneType' object has no attribute 'pesize'

Additional info:

Comment 1 Radek Vykydal 2008-09-24 21:28:36 UTC
seems like same issue as #463780

Comment 2 Radek Vykydal 2008-09-25 13:34:57 UTC

*** This bug has been marked as a duplicate of bug 463780 ***