Bug 1569726

Summary: Network Metrics Isn't collected against any network interface except eth0
Product: OpenShift Container Platform Reporter: Eric Jones <erjones>
Component: NodeAssignee: Solly Ross <sross>
Status: CLOSED WONTFIX QA Contact: DeShuai Ma <dma>
Severity: medium Docs Contact:
Priority: medium    
Version: 3.9.0CC: aos-bugs, dapark, dluong, fdewaley, jforrest, jokerman, mmccomas, sross
Target Milestone: ---Keywords: Unconfirmed
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-05-24 19:02:45 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:
Embargoed:

Description Eric Jones 2018-04-19 22:00:56 UTC
Description of problem:
If there are multiple networking interfaces and/or the primary network interface is anything but eth0  network metrics are not collected.

Version-Release number of selected component (if applicable):
3.9 (but likely impacts other versions)

Additional info:
Open Github issue:
https://github.com/kubernetes/kubernetes/pull/52144

Comment 1 Eric Jones 2018-04-20 14:12:33 UTC
Looking more at the github issue, it seems like they wanted to push that fix into kubernetes 1.9 and looking at one of the files [0], it seems it did, but it seems we might not be taking advantage of it in metrics for OCP 3.9.

I'm not sure how to check if we are querying properly or not though.

[0] https://github.com/kubernetes/kubernetes/blob/release-1.9/pkg/kubelet/apis/stats/v1alpha1/types.go

Comment 7 Solly Ross 2018-05-24 19:05:13 UTC
For public posterity: Unfortunately, Heapster is now deprecated upstream and thus no new RFEs will be accepted.  Adding support for non-default networking stats to Heapster would be a new feature (it's an "add an additional labeled metric for non-default interfaces" or "break the existing metrics schema by making all network metrics labeled").