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.
Bug 1194241 - zFCP LUN with non-system mount point is not brought online during boot
Summary: zFCP LUN with non-system mount point is not brought online during boot
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-blivet
Version: 7.1
Hardware: s390x
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Samantha N. Bueno
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1186677 1205794
TreeView+ depends on / blocked
 
Reported: 2015-02-19 11:49 UTC by Jan Stodola
Modified: 2023-03-08 07:27 UTC (History)
1 user (show)

Fixed In Version: python-blivet-0.61.15.5-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-11-19 08:47:29 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
anaconda.program.log (50.21 KB, text/plain)
2015-02-19 11:51 UTC, Jan Stodola
no flags Details
anaconda.storage.log (554.56 KB, text/plain)
2015-02-19 11:51 UTC, Jan Stodola
no flags Details
zipl.conf (410 bytes, text/plain)
2015-02-19 11:51 UTC, Jan Stodola
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2232 0 normal SHIPPED_LIVE python-blivet bug fix and enhancement update 2015-11-19 09:05:01 UTC

Description Jan Stodola 2015-02-19 11:49:34 UTC
Description of problem:
I've created following partitions during installation, having /mnt/data mount point as the only partition on a FCP LUN (/dev/sda):

[root@rtt7 ~]# lsblk 
NAME     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda        8:0    0    8G  0 disk 
└─sda1     8:1    0    3G  0 part /mnt/data
dasda     94:0    0  2.3G  0 disk 
└─dasda1  94:1    0  2.1G  0 part /
dasdb     94:4    0  2.3G  0 disk 
└─dasdb1  94:5    0  500M  0 part /boot
dasdc     94:8    0  2.3G  0 disk 
└─dasdc1  94:9    0  600M  0 part [SWAP]
[root@rtt7 ~]#

The FCP disk has device number a007, WWPN 0x500507630500c73d and LUN 0x4020400700000000

After reboot, system fails to boot, because the FCP device backing /mnt/data is not freed from the cio_ignore list and brought online:

[root@rtt7 ~]# cat /proc/cio_ignore
0.0.0000-0.0.0008  
0.0.000a-0.0.09ff  
0.0.0a03-0.0.3526  
0.0.3528-0.0.3626  
0.0.3628-0.0.3726  
0.0.3728-0.0.ffff  
0.1.0000-0.1.ffff  
0.2.0000-0.2.ffff  
0.3.0000-0.3.ffff  
[root@rtt7 ~]# 

Version-Release number of selected component (if applicable):
anaconda-19.31.122-1.el7
python-blivet-0.61.0.25-1.el7

How reproducible:
always

Steps to Reproduce:
1. start installation with DASD/FCP devices defined on the kernel command line
2. create partitioning where data mount point (/mnt/data) is the only mount point on a FCP LUN
3. reboot to installed system

Actual results:
system fails to boot, /mnt/data cannot be mounted

Expected results:
system boots without errors

Additional info:
* /etc/zfcp.conf was not created during the installation

Workaround:
1) enter root password to enter emergency mode
2) add a record to /etc/zfcp.conf for every FCP LUN with data (non-system) mount point:
echo "0.0.a007 0x500507630500c73d 0x4020400700000000" >> /etc/zfcp.conf
3) reboot

Comment 1 Jan Stodola 2015-02-19 11:51:02 UTC
Created attachment 993578 [details]
anaconda.log

Comment 2 Jan Stodola 2015-02-19 11:51:06 UTC
Created attachment 993579 [details]
anaconda.packaging.log

Comment 3 Jan Stodola 2015-02-19 11:51:08 UTC
Created attachment 993580 [details]
anaconda.program.log

Comment 4 Jan Stodola 2015-02-19 11:51:22 UTC
Created attachment 993581 [details]
anaconda.storage.log

Comment 5 Jan Stodola 2015-02-19 11:51:24 UTC
Created attachment 993582 [details]
syslog

Comment 6 Jan Stodola 2015-02-19 11:51:40 UTC
Created attachment 993583 [details]
zipl.conf

Comment 9 Jan Stodola 2015-08-27 14:49:26 UTC
Retested on compose RHEL-7.2-20150820.0 with python-blivet-0.61.15.23-1.el7. This issue is fixed and system booted with the following partitioning layout:

[root@rtt7 ~]# lsblk 
NAME     MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda        8:0    0    8G  0 disk 
└─sda1     8:1    0    8G  0 part /mnt/data
dasda     94:0    0  2.3G  0 disk 
└─dasda1  94:1    0  2.3G  0 part /
dasdb     94:4    0  2.3G  0 disk 
└─dasdb1  94:5    0  500M  0 part /boot
dasdc     94:8    0  2.3G  0 disk 
└─dasdc1  94:9    0  2.3G  0 part [SWAP]
[root@rtt7 ~]# cat /etc/zfcp.conf 
0.0.a007 0x500507630500c73d 0x4020400700000000
[root@rtt7 ~]#

Thanks for fixing it, sbueno.
Moving to VERIFIED.

Comment 10 errata-xmlrpc 2015-11-19 08:47:29 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://rhn.redhat.com/errata/RHBA-2015-2232.html


Note You need to log in before you can comment on or make changes to this bug.