Bug 1385232

Summary: NetworkManager does not preserve ifAdminStatus
Product: [Fedora] Fedora Reporter: Frank Ansari <mail>
Component: net-snmpAssignee: Josef Ridky <jridky>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 26CC: dcbw, fgiudici, jridky, jsafrane, lkundrak, thaller, thozza
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-29 11:37:37 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
NetworkManager.log none

Description Frank Ansari 2016-10-15 13:30:00 UTC 
Created attachment 1210772 [details]
NetworkManager.log

Description of problem:
Setting ONBOOT=no in ifcfg file or autoconnect=false in a keyfile does not set IF-MIB::ifAdminStatus to down for snmp. This is a problem for monitoring systems which compare ifAdminStatus with ifOperStatus.

In this example even ifOperStatus is up. Just no IP is assigned because ONBOOT=no.

Version-Release number of selected component (if applicable):
1.2.4

How reproducible:
Disable network interface with ONBOOT=no if you use ifcfg-rh or autoconnect=false if you use keyfile. You might even put the ifAdminStatus down with snmpset. Then restart NetworkManager or reboot your system.

Steps to Reproduce:
1.
2.
3.

Actual results:
--- port name ---------------------------------
IF-MIB::ifName.1 = STRING: lo
IF-MIB::ifName.2 = STRING: p4p1
IF-MIB::ifName.3 = STRING: enp4s0

--- admin status ------------------------------
IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifAdminStatus.2 = INTEGER: up(1)
IF-MIB::ifAdminStatus.3 = INTEGER: up(1)

--- operation status --------------------------
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: up(1)
IF-MIB::ifOperStatus.3 = INTEGER: up(1)


Expected results:
--- port name ---------------------------------
IF-MIB::ifName.1 = STRING: lo
IF-MIB::ifName.2 = STRING: p4p1
IF-MIB::ifName.3 = STRING: enp4s0

--- admin status ------------------------------
IF-MIB::ifAdminStatus.1 = INTEGER: up(1)
IF-MIB::ifAdminStatus.2 = INTEGER: down(2)
IF-MIB::ifAdminStatus.3 = INTEGER: up(1)

--- operation status --------------------------
IF-MIB::ifOperStatus.1 = INTEGER: up(1)
IF-MIB::ifOperStatus.2 = INTEGER: down(2)
IF-MIB::ifOperStatus.3 = INTEGER: up(1)


Additional info:
This works if you use network.service instead of NetworkManager.service. Then you get the expected result.

See also:
https://access.redhat.com/support/cases/#/case/01719751
Comment 1 Thomas Haller 2016-10-15 15:30:13 UTC 
NetworkManager is not involved with snmp.


Anyway, and ifcg-rh file (or a keyfile) is a *connection* to NetworkManager. That is a profile, a bunch of settings how to configure an interface. It is not the interface itself.

You can have multiple connections for the same interface, obviously differing in their connection.autoconnect value.

It's not clear to me that the ifAdminStatus should be based on the "connection.autoconnect" setting.


Reassigning.
Comment 2 Fedora End Of Life 2017-07-25 23:29:28 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

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 24 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 3 Fedora End Of Life 2018-05-03 08:24:49 UTC 
This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

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 26 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 4 Fedora End Of Life 2018-05-29 11:37:37 UTC 
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
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
bug.

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