Bug 1429576

Summary:	No longer force single-language mode in the Atomic install class
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Kolman <mkolman>
Component:	anaconda	Assignee:	Anaconda Maintenance Team <anaconda-maint-list>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.4	CC:	jstodola, mkolman, pkotvan, rvykydal, sbueno
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	anaconda-21.48.22.105-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 08:55:41 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Martin Kolman 2017-03-06 16:11:32 UTC

Description of problem:
In RHELAH 7.3.2, all the officially supported locales will be added
into the tree (see RHBZ#1186757). This means that users should now be
able to specify their language at install time, rather than defaulting
to en_US (which was done for RHBZ#1235726).

Version-Release number of selected component (if applicable):
anaconda-21.48.22.100-1

How reproducible:
always

Steps to Reproduce:
1. run Atomic installation

Actual results:
Atomic installation always runs in single language mode

Expected results:
The user should be able to choose their language at installation time.

Additional info:
There is a PR available, which switches single-language mode OFF for the Atomic install class:
https://github.com/rhinstaller/anaconda/pull/871

Comment 3 Peter Kotvan 2017-05-30 13:37:40 UTC

The patch mentioned in the description is present in anaconda-21.48.22.115-1.el7 moving to VERIFIED (SanityOnly).

Comment 4 errata-xmlrpc 2017-08-01 08:55:41 UTC

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://access.redhat.com/errata/RHBA-2017:2293