Bug 1315494

Summary: C.UTF-8 doesn't actually work as a default locale
Product: [Fedora] Fedora Reporter: Adam Williamson <awilliam>
Component: anacondaAssignee: David Shea <dshea>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: anaconda-maint-list, dshea, g.kaviyarasu, i18n-bugs, jonathan, jsedlak, kparal, mfabian, petersen, projects.rg, robatino, vanmeeuwen+fedora, zbyszek
Target Milestone: ---Keywords: i18n
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://github.com/rhinstaller/anaconda/pull/565
Whiteboard: AcceptedBlocker abrt_hash:b890a9b43d3b8f25b4885fb90b58aecb63638d410c19bc1cd0612d395d5a80b6;
Fixed In Version: anaconda-24.13.2-1 anaconda-24.13.3-1.fc24 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-06 14:06:34 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1230433    
Attachments:
Description Flags
File: anaconda-tb
none
File: anaconda.log
none
File: dnf.log
none
File: environ
none
File: lsblk_output
none
File: nmcli_dev_list
none
File: os_info
none
File: program.log
none
File: storage.log
none
File: syslog
none
File: ifcfg.log
none
File: packaging.log none

Description Adam Williamson 2016-03-07 22:41:37 UTC
Description of problem:
This is a crash from openQA testing of Fedora-Server-dvd-x86_64-Rawhide-20160307.n.0.iso. It crashes immediately upon boot. Note the netinst does not crash in the same way.

Version-Release number of selected component:
anaconda-25.0-1

The following was filed automatically by anaconda:
anaconda 25.0-1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/lib/lang_locale_handler.py", line 142, in _select_locale
    locale_itr = set_treeview_selection(self._localeView, locales[0], col=1)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/spokes/welcome.py", line 205, in initialize
    lang_itr, _locale_itr = self._select_locale(self.data.lang.lang)
  File "/usr/lib64/python3.5/site-packages/pyanaconda/ui/gui/__init__.py", line 827, in run
    self._currentAction.initialize()
  File "/sbin/anaconda", line 1196, in <module>
    anaconda._intf.run()
IndexError: list index out of range

Additional info:
addons:         com_redhat_kdump
cmdline:        /usr/bin/python3  /sbin/anaconda
cmdline_file:   BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-S-dvd-x86_64-rawh quiet
dnf.rpm.log:    Mar 07 22:27:21 INFO --- logging initialized ---
executable:     /sbin/anaconda
hashmarkername: anaconda
kernel:         4.5.0-0.rc6.git3.1.fc25.x86_64
product:        Fedora
release:        Cannot get release name.
type:           anaconda
version:        rawhide

Comment 1 Adam Williamson 2016-03-07 22:41:41 UTC
Created attachment 1133919 [details]
File: anaconda-tb

Comment 2 Adam Williamson 2016-03-07 22:41:42 UTC
Created attachment 1133920 [details]
File: anaconda.log

Comment 3 Adam Williamson 2016-03-07 22:41:43 UTC
Created attachment 1133921 [details]
File: dnf.log

Comment 4 Adam Williamson 2016-03-07 22:41:44 UTC
Created attachment 1133922 [details]
File: environ

Comment 5 Adam Williamson 2016-03-07 22:41:45 UTC
Created attachment 1133923 [details]
File: lsblk_output

Comment 6 Adam Williamson 2016-03-07 22:41:47 UTC
Created attachment 1133924 [details]
File: nmcli_dev_list

Comment 7 Adam Williamson 2016-03-07 22:41:48 UTC
Created attachment 1133925 [details]
File: os_info

Comment 8 Adam Williamson 2016-03-07 22:41:49 UTC
Created attachment 1133926 [details]
File: program.log

Comment 9 Adam Williamson 2016-03-07 22:41:50 UTC
Created attachment 1133927 [details]
File: storage.log

Comment 10 Adam Williamson 2016-03-07 22:41:52 UTC
Created attachment 1133928 [details]
File: syslog

Comment 11 Adam Williamson 2016-03-07 22:41:53 UTC
Created attachment 1133929 [details]
File: ifcfg.log

Comment 12 Adam Williamson 2016-03-07 22:41:54 UTC
Created attachment 1133930 [details]
File: packaging.log

Comment 13 Adam Williamson 2016-03-07 22:46:03 UTC
I'm guessing it's crashing on `locales[0]` here. Interestingly this doesn't seem to happen for me locally - note I'm in Canada, openQA is running in the US.

Comment 14 Adam Williamson 2016-03-07 22:47:11 UTC
note from anaconda.log: "22:27:25,492 DEBUG anaconda: setting locale to: C.UTF-8"

Comment 15 David Shea 2016-03-08 14:30:44 UTC
An easy way to reproduce is to turn off networking. That way geolocation doesn't fix the locale to one that langtable et al can do something with.

Comment 16 Adam Williamson 2016-03-08 15:56:32 UTC
FWIW the "note the netinst does not crash the same way" from the OP was incorrect. in openQA, both DVD and netinst crash this way. For me running locally, neither do (though the locale is still set to C.UTF-8).

Comment 17 David Shea 2016-03-09 15:41:44 UTC
Turns out that it's kind of hard to deal with locale data not actually telling us anything useful! This is going to become an issue in F24, since 5af1a3d9649c1f86a7dbc93a7844842f89c03e5d is on f24-branch as part of the fix for 1312607. However, after the change in lorax to install all glibc langpacks, and the change in glibc to ensure that at least one and most likely all langpacks get installed, anaconda can continue to use en_US.UTF-8 as the default. I'd like to revert that commit on F24 and deal with the more complicated task of handling crazy partially-available locale data on rawhide.

Comment 18 Fedora Blocker Bugs Application 2016-03-09 15:44:19 UTC
Proposed as a Blocker for 24-alpha by Fedora user dshea using the blocker tracking app because:

 This is going to become an issue on alpha any time a user runs in an environment where geolocation data is not available. This causes a crash on the welcome screen, fitting the criterion of "The installer must run when launched normally from the release-blocking images. "

The solution is to revert a commit as outlined in the bug.

Comment 19 Adam Williamson 2016-03-09 16:01:28 UTC
This crash hasn't actually been happening on F24, so far as I can tell.

Comment 20 David Shea 2016-03-09 16:02:55 UTC
It will once there's a new build for F24, though.

Comment 21 Adam Williamson 2016-03-09 17:49:01 UTC
Ah...well, sbueno did build anaconda-24.13.1-1.fc24 today. So should we hold off on doing any composes with that, and wait for a new build with the patch reverted?

Comment 22 Kamil Páral 2016-03-14 17:12:12 UTC
Discussed at today's blocker review meeting [1]. Voted as punt (delay decision) - this isn't a regular "need more info" punt, but the status is that the current stable anaconda does not have this bug so it is not technically a blocker, but if we need a new anaconda package for any other blocker fix, this becomes a blocker and must be fixed.

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-03-14/

Comment 23 Jan Sedlák 2016-03-15 14:26:32 UTC
Still happening in Fedora-Rawhide-20160315.n.0. Doesn't happen in F24.

Comment 25 Adam Williamson 2016-03-23 18:27:33 UTC
Let's move this to the Beta blocker list, now Alpha was signed off with an earlier anaconda build that did not have the bug.

Comment 26 Raphael Groner 2016-03-29 06:09:47 UTC
Is there any doable workaround available? I tend to say this bug should better be proposed as freeze exception, except we do not know how to fix (yet). Can anaconda work with a native code page? Sorry if I did not read all the comments carefully.

Comment 27 Raphael Groner 2016-03-29 06:11:17 UTC
(In reply to David Shea from comment #24)
> https://github.com/rhinstaller/anaconda/pull/565

Okay, this means we could propose as freeze exception (see comment #26), when that upstream patch is not applied before beta freeze.

Comment 28 Stephen Gallagher 2016-03-29 12:39:32 UTC
There's basically zero chance that Beta would not have a newer Anaconda build, so I'm +1 beta blocker for this.

Comment 29 Kamil Páral 2016-03-29 16:54:50 UTC
Discussed at today's blocker review meeting [1]. Voted as AcceptedBlocker (Beta) - this clearly violates the criteria (installer fails to run at all) and it's unlikely we can make the Beta release with the same anaconda build we used for Alpha (which did not suffer from the bug)

[1] https://meetbot-raw.fedoraproject.org/fedora-blocker-review/2016-03-29

Comment 30 Adam Williamson 2016-03-29 23:49:40 UTC
This is now a live issue for F24: anaconda-24.13.1-1.fc24 got pushed stable (autopush due to karma, probably granted by testers who tested by updating live images, which may bypass this bug) and anaconda now fails to run on all F24 images. See all the fails for today's F24 compose:

https://openqa.fedoraproject.org/tests/overview?distri=fedora&version=24&build=Fedora-24-20160329.n.1&groupid=1

could we get a new F24 anaconda build with the fix for this ASAP? Thanks!

Comment 31 Fedora Update System 2016-03-31 19:43:19 UTC
anaconda-24.13.2-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-ed73149773

Comment 32 Raphael Groner 2016-04-03 15:00:10 UTC
*** Bug 1323489 has been marked as a duplicate of this bug. ***

Comment 33 Raphael Groner 2016-04-03 15:16:27 UTC
Tried on a Thinkpad X220 bare metal, anaconda-24.13.2-1.fc24 works for me.

Comment 34 Fedora Update System 2016-04-04 21:25:39 UTC
anaconda-24.13.3-1.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd26edfec7

Comment 35 Fedora Update System 2016-04-05 19:22:14 UTC
anaconda-24.13.3-1.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-cd26edfec7

Comment 36 Fedora Update System 2016-04-06 14:06:14 UTC
anaconda-24.13.3-1.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.