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 1419779 - Lenovo RD650 servers with QLogic HBA deployed RHEL 7.3 hang issue
Summary: Lenovo RD650 servers with QLogic HBA deployed RHEL 7.3 hang issue
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ql23xx-firmware
Version: 7.3
Hardware: x86_64
OS: Unspecified
unspecified
medium
Target Milestone: rc
: ---
Assignee: Peter Martuccelli
QA Contact: Storage QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-07 02:57 UTC by Lan
Modified: 2021-01-15 07:31 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-01-15 07:31:28 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
console error screenshot (78.05 KB, image/png)
2017-02-07 02:57 UTC, Lan
no flags Details

Description Lan 2017-02-07 02:57:29 UTC
Created attachment 1248259 [details]
console error screenshot

Description of problem:
After system deployed with openstack by tool (come with RHEL 7.3 image). Both server went unresponsive after a few hours. Does not response to SysRq for crash dump collection. Power cycle can bring the servers up. And after a few hours it hangs again. HAB error is printed on the console (screenshot attached). Change Qlogic HBA to Emulex, issue resolved. On earlier RHOSP versions, these servers were working fine




Version-Release number of selected component (if applicable):
[heat-admin@overcloud-controller-0 ~]$ cat /sys/class/fc_host/host*/symbolic_name
QLE8242 FW:v4.09.34 DVR:v8.07.00.33.07.3-k1
QLE8242 FW:v4.09.34 DVR:v8.07.00.33.07.3-k1
QLE2672 FW:v7.01.00 DVR:v8.07.00.33.07.3-k1
QLE2672 FW:v7.01.00 DVR:v8.07.00.33.07.3-k1


[heat-admin@overcloud-controller-0 ~]$ modinfo qlcnic|grep version
version:        5.3.65
rhelversion:    7.3
srcversion:     49DB4A010ECB70011DADC66
vermagic:       3.10.0-514.2.2.el7.x86_64 SMP mod_unload modversions 
[heat-admin@overcloud-controller-0 ~]$ modinfo qla2xxx |grep version
version:        8.07.00.33.07.3-k1
rhelversion:    7.3
srcversion:     CB811A8E5529390CA569243
vermagic:       3.10.0-514.2.2.el7.x86_64 SMP mod_unload modversions 


Lenovo server is on latest FW


How reproducible:
On my both Lenovo servers with same model and same HBA cards

Steps to Reproduce:
1. Deployed RHOSP with director come with RHEL 7.3 image
2. Let servers up and running for a few hours, it hangs
3. No response to sysrq. Power cycle the server bring it back, and after a few hours it went unresponsive again

Actual results:


Expected results:


Additional info:

Comment 3 RHEL Program Management 2021-01-15 07:31:28 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.


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