Bug 799606
Summary: | linux can not detect the eth2 failure | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | yijunzhu <yijunzhu> |
Component: | iprutils | Assignee: | Lukáš Nykrýn <lnykryn> |
Status: | CLOSED WONTFIX | QA Contact: | Release Test Team <release-test-team-automation> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.1 | ||
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 16:03:07 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
yijunzhu
2012-03-03 13:46:36 UTC
eth2 is the first port of certain network segment; EG: eth0 belong to net1 eth1 belong to net3 eth2,eth3.....eth20 are from the net3 hope the eth number is not the root cause, but the first port of certain network division maybe the the source of the issue! Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |