Bug 850805 - iproute shows mixed up/down status
iproute shows mixed up/down status
Product: Fedora
Classification: Fedora
Component: iproute (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Pavel Šimerda (pavlix)
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-08-22 08:59 EDT by Bruno Wolff III
Modified: 2015-02-18 08:45 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2015-02-18 08:45:26 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bruno Wolff III 2012-08-22 08:59:19 EDT
Description of problem:
When I try to use netconsole and the OS comes up with the interface names swapped (as defined by hardware address set in the ifcfg-eth* files), eth1 is let in a state that is reported as both up and down. In order to swap the interface names I need to down the device.

It may be that that the two different states are referring to different things and this really isn't a bug.

3: eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT qlen 1000

Version-Release number of selected component (if applicable):
Comment 1 Petr Šabata 2012-08-28 09:21:07 EDT
As with the previous issue, I suppose this is a regression from 3.4?
Comment 2 Bruno Wolff III 2012-08-28 12:58:52 EDT
Actually I think it is an improvement from 3.4 (or maybe the one before that) where I was having worse issues with interfaces that seemed to be both up and down.

I am seeing this more now, because there was a change (in the kernel I suspect) where my interfaces are detected in the reverse order of what they were previously and I have been using netconsole to try to diagnose a few kernel issues.

It's possible that one might not consider this to be an actual bug. (Maybe there are two state spaces that can each be up or down.)
Comment 3 Fedora End Of Life 2013-04-03 15:41:02 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle.
Changing version to '19'.

(As we did not run this process for some time, it could affect also pre-Fedora 19 development
cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.)

More information and reason for this action is here:
Comment 4 Fedora Admin XMLRPC Client 2014-08-20 04:54:00 EDT
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 5 Fedora End Of Life 2015-01-09 17:00:10 EST
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 6 Fedora End Of Life 2015-02-18 08:45:26 EST
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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