Bug 682385

Summary: assumes all ethernet devices are named ethX
Product: Red Hat Enterprise Linux 6 Reporter: Bill Nottingham <notting>
Component: sblim-gatherAssignee: Vitezslav Crhonek <vcrhonek>
Status: CLOSED WONTFIX QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: ovasik, rvokal, vcrhonek
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 682384 Environment:
Last Closed: 2017-12-06 11:54:39 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:
Bug Depends On: 682384    
Bug Blocks: 682269    

Description Bill Nottingham 2011-03-05 02:30:15 UTC 
+++ This bug was initially created as a clone of Bug #682384 +++

Description of problem:

Network devices can have arbitrary names, and due to
http://fedoraproject.org/wiki/Features/ConsistentNetworkDeviceNaming, will have
different names in Fedora 15.

sblim-gather-2.2.2/plugin/cimplugNetworkPort.c:
CMPIObjectPath* COP4VALID (CMPIBroker *broker, const char *id, 
                           const char *systemid)
{
...
  /* use name to determine port type */
  if (strncmp(id,"eth",3)==0) {
    npclass = "Linux_EthernetPort";
  } else if (strncmp(id,"tr",2)==0) {
    npclass = "Linux_TokenRingPort";
  } else if (strncmp(id,"lo",2)==0) {
    npclass = "Linux_LocalLoopbackPort";
  } else {
    npclass = "CIM_NetworkPort";
  }
...

This may not amount to much, depending on how it exposes the difference between a 'Linux_EthernetPort' and a 'CIM_NetworkPort'. But still, devices can be named anything.

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

sblim-gather-2.2.2

How reproducible:

By code inspection.
Comment 2 RHEL Program Management 2011-03-05 02:58:40 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 5 Suzanne Logcher 2012-02-14 23:07:36 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. 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. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 7 Jan Kurik 2017-12-06 11:54:39 UTC 
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/