Bug 1330198 - Several systems report Key/Values "NR_ETH" as 0 when run with RHEL 7.2
Summary: Several systems report Key/Values "NR_ETH" as 0 when run with RHEL 7.2
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Beaker
Classification: Retired
Component: inventory
Version: 22
Hardware: All
OS: All
unspecified
high vote
Target Milestone: ---
Assignee: beaker-dev-list
QA Contact: tools-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-25 15:13 UTC by Arthur Benoit
Modified: 2020-10-21 14:17 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-10-21 14:13:47 UTC


Attachments (Terms of Use)

Description Arthur Benoit 2016-04-25 15:13:25 UTC
Description of problem:
Several systems report NR_ETH as 0 when run with RHEL 7.2. See jobs:
J:1314086, J:1318464, J:1313913 and J:1312869 Note J:131431

Note I do see one system J:1314319 which shows NR_ETH appears to have been updated.


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

How reproducible:
Not always

Steps to Reproduce:
1. Clone any of the jobs above
2. look at the NR_ETH entry on the Key/Values tab.

Actual results:
NR_ETH incorrectly reports the number of Ethernet ports on the system.

Expected results:
NR_ETH should correctly report the number of Ethernet ports on the system.

Comment 1 Arthur Benoit 2016-04-25 15:17:53 UTC
Note rfreiss reported that this has been seen in RHEL 6.8 as well.

Comment 2 Dan Callaghan 2016-04-27 04:17:30 UTC
I checked on a RHEL7.2 VM I have here and I get NR_ETH=1, so it seems like this must be a hardware-specific problem.

I don't have access to any of the Beaker systems mentioned in comment 0. Arthur, could you please pick one and loan it to me and so I can investigate further?


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