| Summary: | makes assumptions about network devices that may not be valid | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Bill Nottingham <notting> |
| Component: | iscsi-initiator-utils | Assignee: | Chris Leech <cleech> |
| Status: | CLOSED WONTFIX | QA Contact: | Storage QE <storage-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.1 | CC: | coughlan, fge, mchristi, rvokal |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | powerpc | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-12-06 10:17:01 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Bug Depends On: | |||
| Bug Blocks: | 767187 | ||
I think you are right, but I am not that familiar with ppc. The patch came from IBM. I will check out a box and play around some to verify. Since RHEL 6.1 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. Red Hat Enterprise Linux 6 is in the Production 3 Phase. 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 meet the inclusion criteria for the Production 3 Phase 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. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL: https://access.redhat.com/ |
Description of problem: open-iscsi-2.0-872-rc4-bnx2i/utils/fwparam_ibft/fwparam_ppc.c This generates a list of network devices by searching openfirmware and sorting them into a 'niclist' array. It then searches for the boot dev path and does: for (ndx = 0; ndx < nic_count; ndx++) { if (!strcmp(niclist[ndx], ofwdev->dev_path)) { snprintf(context->iface, sizeof(context->iface), "eth%d", ndx); break; } } Problems: 1) It assumes that the network device will be in the ethX space. While we do not do any renaming out of this namespace by default on ppc, it's possible the administrator may decide to rename devices. 2) It assumes a zero-based, monotonically increasing set of devices (such that the first device is eth0, the second device will be eth1, the third eth2, and so on. Given persistent mappings of device <-> hardware address, hardware swaps & changes in configuration could cause this to not be true, even if every device is in the ethN space. I may be misunderstanding what this is doing, feel free to correct me. Version-Release number of selected component (if applicable): iscsi-initiator-utils-6.2.0.872-17.el6 How reproducible: Have not attempted to reproduce in the wild; this was done by code inspection.