Bug 1814044

Summary:	Check that 4.5 (based on kube 1.18) does not make unnecessary calls to the cloud provider
Product:	OpenShift Container Platform	Reporter:	Maru Newby <mnewby>
Component:	Networking	Assignee:	Miciah Dashiel Butler Masters <mmasters>
Networking sub component:	router	QA Contact:	Hongan Li <hongli>
Status:	CLOSED WONTFIX	Docs Contact:
Severity:	medium
Priority:	medium	CC:	amcdermo, aos-bugs, bbennett
Version:	4.5
Target Milestone:	---
Target Release:	4.7.0
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:	2020-10-02 15:43:16 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:
Bug Depends On:
Bug Blocks:	1798282

Description Maru Newby 2020-03-16 20:53:13 UTC

Previous to 4.5, openshift/kubernetes was carrying the equivalent of [1]. That PR was closed in favor of [2], so that carry was dropped for 4.5. Please confirm that the unnecessary calls to the cloud provider cannot be reproduced in the absence of the carry.

1: https://github.com/kubernetes/kubernetes/pull/63926
2: https://github.com/kubernetes/kubernetes/pull/78262

Comment 1 Miciah Dashiel Butler Masters 2020-05-19 01:00:32 UTC

I'm not sure how to deal with this report (bug 1814044).  The request is essentially asking for confirmation that https://github.com/openshift/origin/pull/24532 does not cause a regression of bug 1571940.  Options to "fix" it could include the following:

• Test the PR manually, use CloudTrail to monitor API usage, and compare it to 4.4 (for example).

• Write a CI test that checks API usage (if this possible) and warns if it is above some threshold.

• Wait till https://github.com/openshift/origin/pull/24532 merges, then move bug 1814044 to ON_QA and let QE verify that bug 1571940 is still fixed.

Ben, do you have any guidance?

Comment 2 Andrew McDermott 2020-05-19 14:59:27 UTC

Moving to 4.6.

Comment 3 Miciah Dashiel Butler Masters 2020-06-18 19:31:03 UTC

Let's try to clarify the expectations for resolving this report in the upcoming sprint.

Comment 4 Miciah Dashiel Butler Masters 2020-07-09 05:01:44 UTC

Still seeking clarification on the expectations for resolving this report.

Comment 5 Miciah Dashiel Butler Masters 2020-07-30 08:29:47 UTC

Still need info on the expectations for resolving this report.

Comment 6 mfisher 2020-08-18 19:55:56 UTC

Target reset to 4.7 while investigation is either ongoing or not yet started.  Will be considered for earlier release versions when diagnosed and resolved.

Comment 7 Miciah Dashiel Butler Masters 2020-08-21 05:03:55 UTC

Still blocked on needinfo.

Comment 8 Andrew McDermott 2020-09-10 11:57:59 UTC

I’m adding UpcomingSprint, because I was occupied by fixing bugs with
higher priority/severity, developing new features with higher
priority, or developing new features to improve stability at a macro
level. I will revisit this bug next sprint.

Comment 9 Andrew McDermott 2020-10-02 15:43:16 UTC

We plan to close this as no responses to needinfo requests made in comment #1 and subsequent comments. Please feel free to reopen if there are any outstanding concerns.

Comment 10 Red Hat Bugzilla 2023-09-15 01:29:16 UTC

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 365 days