Bug 1009897
| Summary: | Adding zFCP device fails on s390x guest with one CPU | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Stodola <jstodola> |
| Component: | s390utils | Assignee: | Dan Horák <dhorak> |
| Status: | CLOSED ERRATA | QA Contact: | Branislav Blaškovič <bblaskov> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.5 | CC: | bblaskov, mganisin, pknirsch, sbueno, secondary-arch-list, tlavigne |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | s390x | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | s390utils-1.8.2-52.el6 | Doc Type: | Bug Fix |
| Doc Text: |
Cause: incorrect order of initialization for zFCP disks
Consequence: presence of zFCP disk not detected by Anaconda
Fix: use cio_settle kernel interface to wait for the zFCP device to come online.
Result: Anaconda sees the zFCp devices.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-10-14 07:35:27 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 972747 | ||
|
Description
Jan Stodola
2013-09-19 12:54:19 UTC
Code from storage/zfcp.py:
...
if not os.path.exists(online):
log.info("Freeing zFCP device %s" % (self.devnum,))
iutil.execWithRedirect("zfcp_cio_free", ["-d", self.devnum],
stdout="/dev/tty5", stderr="/dev/tty5")
if not os.path.exists(online):
raise ValueError, _(
"zFCP device %s not found, not even in device ignore list."
%(self.devnum,))
...
Reproduced manually:
[anaconda root@rtt7 root]# zfcp_cio_free -d a107; ls /sys/bus/ccw/drivers/zfcp/; sleep 1; ls /sys/bus/ccw/drivers/zfcp/
ls: cannot access /sys/bus/ccw/drivers/zfcp/: No such file or directory
0.0.a107 bind module uevent unbind
[anaconda root@rtt7 root]#
I'm not sure if this is problem in anaconda/s390-utils/kernel, please reassign if necessary.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux. I don't believe anaconda is the correct component for this; the issue seems to be at a lower level than the installer. My assumption would be s390utils; reassigning. Jan, I guess it's the same issue as in 1054691. Yes, it looks so. Not able to reproduce any more with s390utils-1.8.2-54.el6 on a system with one CPU: [root@rtt7 ~]# cat /proc/cpuinfo vendor_id : IBM/S390 # processors : 1 bogomips per cpu: 2913.00 features : esan3 zarch stfle msa ldisp eimm dfp etf3eh highgprs processor 0: version = FF, identification = 11C047, machine = 2827 [root@rtt7 ~]# [root@rtt7 ~]# rpm -q s390utils s390utils-1.8.2-54.el6.s390x [root@rtt7 ~]# [root@rtt7 ~]# zfcp_cio_free -d a107; ls /sys/bus/ccw/drivers/zfcp/; sleep 1; ls /sys/bus/ccw/drivers/zfcp/ 0.0.a107 bind module uevent unbind 0.0.a107 bind module uevent unbind [root@rtt7 ~]# Also adding zFCP disk during installation works fine. Not moving to VERIFIED in case you want to run additional tests. Switching to VERIFIED as jstodola already verified this. 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-2014-1546.html |