RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
When /boot is a logical volume and non-C (or non-english) locale is used then zipl fails with an error.

[root@devel2 ~]# zipl
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot/
Error: Could not determine partition start for dasda1
Error: Script could not determine target parameters


Version-Release number of selected component (if applicable):
s390utils-1.8.2-36.el6.s390x

How reproducible:
100%

Steps to Reproduce:
1. zipl
  
Actual results:
[root@devel2 ~]# zipl
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot/
Error: Could not determine partition start for dasda1
Error: Script could not determine target parameters

Expected results:
[root@devel2 ~]# LANG=C zipl
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot/
Building bootmap in '/boot/'
Building menu 'rh-automatic-menu'
Adding #1: IPL section 'linux-2.6.32-131.0.15.el6.s390x' (default)
Preparing boot device: dasda.
Done.

Created attachment 517826 [details]
run helper script in C locale

My locale is "cs_CZ.UTF-8" and the tool with translated output is blockdev.

Created attachment 519007 [details]
s390-tools-rhel6-zipl_helper_locale.patch


------- Comment on attachment From brueckner.ibm.com 2011-08-19 06:31 EDT-------


Description: zipl: localized scripting output leads to errors
Symptom:     zipl is terminated with an error:
	     "Script could not determine target parameters"
Problem:     zipl uses zipl_helper.device-mapper to print zipl parameters 
	     for device mapper devices. This script parses the output
	     of other programs that might have a locale dependent
	     output. If so, the script is unable to parse the output.
Solution:    Setup and use a standard locale to avoid localized
	     scripting output.

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.

http://rhn.redhat.com/errata/RHBA-2011-1525.html