Bug 503777
| Summary: | AttributeError while resizing software RAID partition | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Zack Cerza <zcerza> | ||||
| Component: | anaconda | Assignee: | Hans de Goede <hdegoede> | ||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 11 | CC: | rmaximo, vanmeeuwen+fedora | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | anaconda_trace_hash:ee6e5987461799c6a2e06b4c6a30cb91fbdada77e6c01ae217444ab80bf32cf4 | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2010-03-15 13:21:01 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: |
|
||||||
Created attachment 346282 [details]
Attached traceback automatically from anaconda.
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle. Changing version to '11'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping We just did a quick test here and were unable to reproduce this error. All attempts to resize a RAID member or the filesystem on top of the RAID member were prevented by anaconda. Can you outline the UI steps you took that led to this traceback? Thanks. I can't say for sure that I remember accurately (perhaps Anaconda should log UI events?), but I'll try. Here's what I remember. I had 2 disks: sda and sdb. I put /boot on sda, and used the remaining space to create two software RAID members - one on each disk. I then created a RAID0 array from the two members and indicated that it should be formatted btrfs. When I clicked on Forward, I was warned that I'd forgotten to create a swap partition. So I hit Cancel (or whatever the "go back" button is called in that dialog) and attempted to resize the member that was on sdb. Traceback. But whatever happened, I suspect that MDRaidMember should not simply be missing attributes; otherwise you'll have to constantly catch AttributeErrors. Closing this as insufficient data, as no reproduction instructions have been provided (and the last comment is more then 6 months old). |
The following was filed automatically by anaconda: anaconda 11.5.0.57 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/deviceaction.py", line 345, in __init__ if device.format.targetSize == newsize: File "/usr/lib/anaconda/iw/partition_dialog_gui.py", line 295, in run actions.append(ActionResizeFormat(request, size)) File "/usr/lib/anaconda/iw/partition_gui.py", line 1119, in editPartition actions = parteditor.run() File "/usr/lib/anaconda/iw/partition_gui.py", line 1080, in editCB self.editPartition(device) AttributeError: 'MDRaidMember' object has no attribute 'targetSize'