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.
Description of problem:
ixgbe nic is falsely advertising MII support and is causing an error in OVS where failover won't behave as expected.
An ixgbe maintainer wrote a patch [1] and the OVS team is asking me to test this patch with the customer. Would it be possible to merge this patch?
http://patchwork.ozlabs.org/patch/664633/
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Create a OVS bridge while bonding two ixgbe nics
2. Unplug one of the cables
3.
Actual results:
Failover is failing
Expected results:
Failover should work
Additional info:
Travis,
The patch mentioned in the description has not made it upstream yet. This is reported to fix this bug for the customer.
Can we ping Intel and get status?
After consulting with the author, this patches status was incorrectly changed. I currently have the patch going through validation and should be pushed upstream to David Miller later this week.
The patch has been pushed upstream and has been accepted by David Miller into his "net" tree. Here is the commit information:
commit e0f06bba9629
Author: Mark Rustad <mark.d.rustad>
ixgbe: Return error when getting PHY address if PHY access is not supported
Reproduce this bug at kernel 3.10.0-327.el7.x86_64, close the physical switch port that connect to the ixgbe interface to simulate the unplug cable.
Verify it is be fixed at kernel 3.10.0-748.el7.x86_64.
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.
https://access.redhat.com/errata/RHSA-2018:1062