Bug 1439060
| Summary: | ValueError: Size limit must be greater than zero. | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Pavel Holica <pholica> | ||||||||||||
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 26 | CC: | anaconda-maint-list, g.kaviyarasu, jonathan, jvavra, mkolman, vanmeeuwen+fedora, vponcova, vtrefny | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:fe73238df1cd4ae1a626cc7a7de4da04d11e5b74dcafe4f2de0e37fca744051f; | ||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2017-04-05 07:28:40 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 1268861 [details]
File: anaconda-tb
Created attachment 1268862 [details]
File: environ
Created attachment 1268863 [details]
File: lsblk_output
Created attachment 1268864 [details]
File: nmcli_dev_list
Created attachment 1268865 [details]
File: os_info
I've tried this in alpha compose. Similar problem has been detected: VM with three drives each 10G. virtio,scsi,sata. Visited blivet gui. Created 1G /boot partition on vda. Selected creation of softwaee raid across all three drives. Chosen lvm as the filesystem over the raid. BAM! exception. addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda hashmarkername: anaconda kernel: 4.11.0-0.rc3.git0.2.fc26.x86_64 package: anaconda-26.21.1-1 product: Fedora reason: ValueError: Size limit must be greater than zero. release: Cannot get release name. version: 26 *** This bug has been marked as a duplicate of bug 1430349 *** |
Description of problem: In blivet-gui: I created 1G large xfs /boot Then clicked on "free space" and "+" button. Selected "physical volume (LVM)" as Filesystem. Traceback appeared. I've been clicking to the gui before then trying some things, so this may not be all the required steps. Version-Release number of selected component: anaconda-26.21.1-1 The following was filed automatically by anaconda: anaconda 26.21.1-1 exception report Traceback (most recent call first): File "/usr/lib/python3.6/site-packages/blivetgui/dialogs/size_chooser.py", line 208, in max_size_limit raise ValueError("Size limit must be greater than zero.") File "/usr/lib/python3.6/site-packages/blivetgui/dialogs/add_dialog.py", line 773, in on_filesystems_combo_changed self.size_area.max_size_limit = self._get_max_size_limit() ValueError: Size limit must be greater than zero. Additional info: addons: com_redhat_kdump, com_redhat_docker cmdline: /usr/libexec/system-python /sbin/anaconda executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.11.0-0.rc3.git0.2.fc26.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 26