Bug 1703512

Summary: Request backport of https://github.com/kubernetes/kubernetes/pull/77069
Product: OpenShift Container Platform Reporter: Jim Minter <jminter>
Component: Cloud ComputeAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: Mike Gahagan <mgahagan>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: agarcial, gblomqui, jhou, mifiedle
Target Milestone: ---   
Target Release: 3.11.z   
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: 2019-09-03 15:56:02 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 Jim Minter 2019-04-26 15:41:31 UTC
Please backport https://github.com/kubernetes/kubernetes/pull/77069 to OCP 3.11.

It provides substantial robustness fixes when managing Azure OpenShift clusters using VM scale sets.

Comment 1 Jan Chaloupka 2019-05-02 14:37:06 UTC
Backporting PR: https://github.com/openshift/origin/pull/22742

Comment 2 Jim Minter 2019-08-07 16:43:01 UTC
Additional notes: backporting kubernetes/kubernetes#77069 enables use of a new Microsoft API for VMSS management which was not GA at the point where 1.11 was released. Using this API removes an entire class of race conditions from OpenShift/VMSS and hence ARO cluster management.

By inspection, I am confident in the Microsoft team's decision-making wrt the additional 1.11 fixes that we would like to backport here. They improve upstream robustness; applying them here will remove the delta between us and upstream (having a delta is not in our favour) and make it easier to collaborate with MSFT on any issues raised on this codebase in the future.

Comment 4 Jianwei Hou 2019-08-28 03:23:47 UTC
We don't find regressions on azure 3.11.141. Mark as verified.

Comment 6 errata-xmlrpc 2019-09-03 15:56:02 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2580