Hide Forgot
Created attachment 1132727 [details] full log Description of problem: Anaconda fails after clicking "Full disk summary and boot loader... on "Instalaltion destination" spoke. Version-Release number of selected component (if applicable): anaconda-21.48.22.56-1 python-blivet-0.61.15.37-1 How reproducible: always Steps to Reproduce: 1. Starts anaconda 2. Select Russian language 3. Go to "INSTALLATION DESTINATION" spoke 4. Click "Full disk summary and boot loader" in left bottom Actual results: Unhandled exception handler appears with msg: anaconda 21.48.22.56-1 exception report Traceback (most recent call first): File "/usr/lib/python2.7/site-packages/blivet/size.py", line 175, in _parseSpec raise ValueError("invalid size specification", spec) File "/usr/lib/python2.7/site-packages/blivet/size.py", line 204, in __new__ size = _parseSpec(value) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/cart.py", line 128, in _update_summary size += Size(row[SIZE_COL]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/cart.py", line 68, in initialize self._update_summary() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/lib/cart.py", line 107, in refresh self.initialize(disks, free, showRemove=showRemove, setBoot=setBoot) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 708, in on_summary_clicked free_space) ValueError: ('invalid size specification', '10 \xd0\x93\xd0\xb8\xd0\x91') Expected results: Full disk summary and boot loader dialog appears. Additional info: Looks like anaconda calls blivet's Size() function with translated size ("10 гиб"), while blivet checks for ascii-encondig and handle only en-names size (Gib/Kib and so on).
Anaconda also fails with kz-language. Looks like just few languages have translation of "GiB" and it appears somewhere between anaconda ~ blivet (and last one handle just latin MiB/GiB names).
*** Bug 1334919 has been marked as a duplicate of this bug. ***
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. https://rhn.redhat.com/errata/RHBA-2016-2168.html