Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 958897
Summary: | TypeError: __init__() got an unexpected keyword argument 'container_raid_level' | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Reartes Guillermo <rtguille> | ||||||||||||||||||||||||||||
Component: | python-blivet | Assignee: | David Lehman <dlehman> | ||||||||||||||||||||||||||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||||||||||
Version: | 19 | CC: | awilliam, bcl, bitlord0xff, bugzilla, clydekunkel7734, dan.mashal, dlehman, g.kaviyarasu, jonathan, kuba.herbstrait, mkolman, robatino, sbueno, vanmeeuwen+fedora | ||||||||||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||||||||||
Whiteboard: | abrt_hash:6cca79298a9b749b8eca94636cb781d34325747eecde69e4055583bde4c42b08 AcceptedBlocker | ||||||||||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||||||||||
Last Closed: | 2013-05-13 17:16:06 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: | |||||||||||||||||||||||||||||||
Bug Depends On: | |||||||||||||||||||||||||||||||
Bug Blocks: | 834087 | ||||||||||||||||||||||||||||||
Attachments: |
|
Description
Reartes Guillermo
2013-05-02 15:43:08 UTC
Created attachment 742772 [details]
File: anaconda.log
Created attachment 742773 [details]
File: backtrace
Created attachment 742774 [details]
File: environ
Created attachment 742775 [details]
File: ifcfg.log
Created attachment 742776 [details]
File: lsblk_output
Created attachment 742777 [details]
File: nmcli_dev_list
Created attachment 742778 [details]
File: packaging.log
Created attachment 742779 [details]
File: program.log
Created attachment 742780 [details]
File: storage.log
Created attachment 742781 [details]
File: syslog
Created attachment 742782 [details]
File: anaconda-tb
Created attachment 742783 [details]
screenshot of what triggered the crash
after doing this, anaconda crashes some seconds later.
*** Bug 958956 has been marked as a duplicate of this bug. *** Description of problem: start with 80GB virtual disk 1. Installation options, partition scheme BTRFS. 2. Manual partitioning, click + to add a partition. 3. Enter / and 82gb in the dialog, click OK. Crash. Version-Release number of selected component: anaconda-19.23-1.fc19.x86_64 Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-osimg-min --lang en_US.UTF-8 cmdline_file: initrd=initrd0.img root=live:CDLABEL=Fedora-Live-Desktop-x86_64-19-Be rootfstype=auto ro rd.live.image quiet rhgb rd.luks=0 rd.md=0 rd.dm=0 BOOT_IMAGE=vmlinuz0 core_backtrace: executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64 other involved packages: python-blivet-0.11-1.fc19.noarch packaging.log: product: Fedora release: Fedora release 19 (Schrödinger’s Cat) type: anaconda ureports_counter: 1 version: 19 Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1907, in on_add_clicked self._do_refresh(mountpointToShow=mountpoint) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 894, in _do_refresh self.on_page_clicked(firstPage, mountpointToShow=mountpointToShow) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2308, in on_page_clicked self._save_current_selector() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2231, in _save_current_selector self._save_right_side(self._current_selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1237, in _save_right_side selector=selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 957, in _replace_device new_device = self.__storage.factoryDevice(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1875, in factoryDevice **kwargs) File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 97, in get_device_factory return factory_class(blivet, size, disks, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 1175, in __init__ super(BTRFSFactory, self).__init__(storage, size, disks, **kwargs) TypeError: __init__() got an unexpected keyword argument 'container_raid_level' *** Bug 958960 has been marked as a duplicate of this bug. *** Description of problem: In partitioner deleted premade btrfrs partition, recreated it, added a label, clicked Update Settings and screen froze, then after awhile this error. Version-Release number of selected component: anaconda-19.23-1 Additional info: cmdline: /usr/bin/python /sbin/anaconda cmdline_file: initrd=initrd.img inst.stage2=hd:UUID=afbcf488-11c6-4c3c-8c51-f8ef83d1920a selinux=0 BOOT_IMAGE=vmlinuz executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.9.0-0.rc8.git0.2.fc19.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 19-Beta-TC2 Truncated backtrace: Traceback (most recent call last): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2624, in on_apply_clicked self._save_right_side(self._current_selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1237, in _save_right_side selector=selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 957, in _replace_device new_device = self.__storage.factoryDevice(*args, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/__init__.py", line 1875, in factoryDevice **kwargs) File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 97, in get_device_factory return factory_class(blivet, size, disks, **kwargs) File "/usr/lib/python2.7/site-packages/blivet/devicefactory.py", line 1175, in __init__ super(BTRFSFactory, self).__init__(storage, size, disks, **kwargs) TypeError: __init__() got an unexpected keyword argument 'container_raid_level' At least some of the bug descriptions sound severe enough to infringe our Beta custom part criteria: https://fedoraproject.org/wiki/Fedora_19_Beta_Release_Criteria#Custom_partitioning "When using the custom partitioning flow, the installer must be able to: Correctly interpret, and modify as described below, any disk with a valid ms-dos or gpt disk label and partition table containing ext4 partitions, LVM and/or btrfs volumes, and/or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions Create mount points backed by ext4 partitions, LVM volumes or btrfs volumes, or software RAID arrays at RAID levels 0, 1 and 5 containing ext4 partitions Remove a planned storage volume from the planned layout Assign sizes to newly-created storage volumes and containers Encrypt newly-created storage volumes Remove existing storage volumes Assign mount points to existing storage volumes Reject or disallow invalid disk and volume configurations without crashing." So proposing as a Beta blocker. *** Bug 959038 has been marked as a duplicate of this bug. *** *** Bug 958999 has been marked as a duplicate of this bug. *** This is fixed by the set of patches I have currently under review. *** Bug 959441 has been marked as a duplicate of this bug. *** *** Bug 959537 has been marked as a duplicate of this bug. *** Would an updates.img be appropriate? TIA well, I think they're reviewing the patches atm, so I don't want to get in the way of that. we should be able to roll a new anaconda and TC3 pretty quickly after they land. https://www.happyassassin.net/extras/updates-958897.img includes dlehman's changes (and various others too). Let us know if it fixes the bug. Thanks! We should get a new anaconda build this afternoon. (In reply to comment #25) > https://www.happyassassin.net/extras/updates-958897.img This plus updating to python-meh-0.24 to fix the libreport failure, I end up with a crash on launch of anaconda, hitting bug 959552. Try this instead: https://www.happyassassin.net/extras/updates-958897-2.img it includes blivet changes as well, should work better. If I did it right. (In reply to comment #27) > Try this instead: > https://www.happyassassin.net/extras/updates-958897-2.img I still get a crash that sends me to (this) bug 958897, however my path to trigger this bug is totally different than this bug's description. The way I'm triggering it is bug 958956. (In reply to comment #28) Nevermind, appears to be user error typing in the updates= line. I also cannot run the updates image, most likely i am making a typo somewhere but i can't find it. Nope it's still crashing on me, just not as often, and it comes back to this bug. Can you attach the /tmp/anaconda-tb-* file from your traceback? Can you also double-check that /tmp/updates exists, is populated, and contains a 'blivet' folder? I can definitely reproduce this without the updates.img , but not with it so far. Created attachment 743373 [details]
anaconda-tb-kApnwr with updates-958897-2.img
Confirm updates folder contains blivet folder. Under the updates folder is a 354469 byte updates.img file. The first crash I got with the update occurred quickly, this one took maybe 5-6 minutes of clicking around. The main thing that sees to trigger it, some of the time, is with multiple devices selected, creating a root that's bigger than any one device, and trying to make it LVM - this causes the whole mountpoint to vanish and maybe a minute later if I don't do anything else I get a crash.
cmurf: that's pretty clearly not the same traceback as this one (so if libreport really considers it a dupe of this one, that seems like a bug). dlehman says if you can file a new report, that'd be best. thanks! anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19 after changing https to http, I got the updates image to load and had a successful install. Cool banners at the bottom while installing packages. Huh. I think my SSL certs are in order. I wonder if it's a problem pulling update images via https from *my* server, or pulling them via https from *any* server... (In reply to comment #38) > Huh. I think my SSL certs are in order. I wonder if it's a problem pulling > update images via https from *my* server, or pulling them via https from > *any* server... With https I would either get a hang with no further msgs or get a msg that file was found, then it would either just hang after the statistics headers or I would get a msg: 0curl: (77)Problem with the SSL CA cert (path? access rights?). This latter msg caused me to use http. Package anaconda-19.24-1.fc19, python-blivet-0.12-1.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing anaconda-19.24-1.fc19 python-blivet-0.12-1.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-7403/python-blivet-0.12-1.fc19,anaconda-19.24-1.fc19 then log in and leave karma (feedback). Discussed at 2013-05-06 blocker review meeting: http://meetbot.fedoraproject.org/fedora-blocker-review/2013-05-06/f19beta-blocker-review-3.2013-05-06-16.02.log.txt . Accepted as a blocker per criteria cited in comment #17. Seems pretty clear that this is fixed in TC3, so setting VERIFIED. Seems fixed. Will wait for TC4 to call it so. 19.25 went stable, let's close this. |