Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Red Hat Enterprise Linux 6 transitioned to the Production 3 Phase on May 10, 2017. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not appear to meet the inclusion criteria for the Production Phase 3 and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com
Description of problem: When using "rescan-scsi-bus.sh -a" command to attach LUN assigned from the storage, the LUNs are attached to the system, however it always shows "0 new or changed device(s) found." as output. Version-Release number of selected component (if applicable): - System: Red Hat Enterprise Linux Server release 6.6 (Santiago) - Kernel: 2.6.32-504.el6.x86_64 - Packages: - sg3_utils-1.28-12.el6.x86_64 - sg3_utils-libs-1.28-12.el6.x86_64 - Script: rescan-scsi-bus.sh Steps to Reproduce: 1. The storage administrator did the zoning and masking at a switch level; 2. Made the LUN then assign the new LUN to the server; 3. Run rescan-scsi-bus.sh -a 4. LUNs are attached to the system, but it shows "0 new or changed device(s) found." Actual results: # rescan-scsi-bus.sh -a Scanning SCSI subsystem for new devices Scanning host 0 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 0 2 0 0 ... OLD: Host: scsi0 Channel: 02 Id: 00 Lun: 00 Vendor: DELL Model: PERC H730 Mini Rev: 4.26 Type: Direct-Access ANSI SCSI revision: 05 Scanning host 1 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 2 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 3 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 4 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 5 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 6 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 7 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 8 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 9 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 10 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning host 11 for SCSI target IDs 0 1 2 3 4 5 6 7, all LUNs Scanning for device 11 0 0 0 ... OLD: Host: scsi11 Channel: 00 Id: 00 Lun: 00 Vendor: iDRAC Model: Virtual CD Rev: 0329 Type: CD-ROM ANSI SCSI revision: -1 Scanning for device 11 0 0 1 ... OLD: Host: scsi11 Channel: 00 Id: 00 Lun: 01 Vendor: iDRAC Model: Virtual Floppy Rev: 0329 Type: Direct-Access ANSI SCSI revision: -1 Scanning host 12 for all SCSI target IDs, all LUNs Scanning for device 12 0 0 0 ... OLD: Host: scsi12 Channel: 00 Id: 00 Lun: 00 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 12 0 0 1 ... OLD: Host: scsi12 Channel: 00 Id: 00 Lun: 01 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 12 0 0 2 ... OLD: Host: scsi12 Channel: 00 Id: 00 Lun: 02 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 12 0 0 3 ... OLD: Host: scsi12 Channel: 00 Id: 00 Lun: 03 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning host 13 for all SCSI target IDs, all LUNs Scanning for device 13 0 0 0 ... OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 00 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 13 0 0 1 ... OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 01 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 13 0 0 2 ... OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 02 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 Scanning for device 13 0 0 3 ... OLD: Host: scsi13 Channel: 00 Id: 00 Lun: 03 Vendor: HITACHI Model: OPEN-V Rev: 7303 Type: Direct-Access ANSI SCSI revision: 03 0 new or changed device(s) found. 0 remapped or resized device(s) found. 0 device(s) removed. Expected results: [...] 2 new or changed device(s) found. 0 remapped or resized device(s) found. 0 device(s) removed. Additional info: