Bug 1825976

Summary: etcd quorum guard: should not use hostNetwork
Product: OpenShift Container Platform Reporter: Sam Batschelet <sbatsche>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED WONTFIX QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.5CC: geliu, skolicha
Target Milestone: ---   
Target Release: 4.4.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1825967 Environment:
Last Closed: 2020-05-20 13:57:28 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: 1825967    
Bug Blocks:    

Description Sam Batschelet 2020-04-20 15:48:22 UTC
+++ This bug was initially created as a clone of Bug #1825967 +++

Description of problem: because quorum-guard is using hostNetwork all network traffic to be counted as a container traffic, so some pods had > 4MBps network in/out in console.


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results: quorum-guard preforms localhost checks against host 127.0.0.1 
 and is counted as container traffic.


Expected results:quorum-guard preforms localhost checks against host 127.0.0.1 without be counted as container traffic.


Additional info:

--- Additional comment from Sam Batschelet on 2020-04-20 15:40:16 UTC ---

Verification steps.

stand up prometheus based on prom data file from the following PR run.

https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1552/pull-ci-openshift-machine-config-operator-master-e2e-aws/6758

query
container_network_transmit_bytes_total{name="k8s_POD_etcd-quorum-guard-f9fc8d4c-6x4g5_openshift-machine-config-operator_a7a8ac88-81ac-4b37-bdc9-e148c88a53e7_0"}

result is max of about 483.9 k of traffic.

see attached file (4.5-fixed.png)

Before this patfch you can see container traffic in the hundreds of mb see (4.5-before-fix.png)

--- Additional comment from Sam Batschelet on 2020-04-20 15:41:34 UTC ---



--- Additional comment from Sam Batschelet on 2020-04-20 15:42:49 UTC ---



--- Additional comment from ge liu on 2020-04-20 15:45:55 UTC ---

Verified with steps of Sam updated, thanks!

Comment 1 Scott Dodson 2020-04-24 13:10:57 UTC
Based on the discussion in the PR there's no ill effect of this in 4.4, moving target release to 4.4.z. The PR is also held which supports this action as well.

Comment 5 Red Hat Bugzilla 2023-09-14 05:55:43 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days