Bug 1595599

Summary: [3.7] Error creating subnet for node - just error message in logs - OCP on Azure
Product: OpenShift Container Platform Reporter: Jan Chaloupka <jchaloup>
Component: Cloud ComputeAssignee: Jan Chaloupka <jchaloup>
Status: CLOSED ERRATA QA Contact: DeShuai Ma <dma>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 3.7.0CC: aos-bugs, bjarolim, bleanhar, borisb, clasohm, dcbw, dkinkead, dma, grodrigu, harold.wong, jawilson, jchaloup, jenander, jokerman, mfojtik, misalunk, mmccomas, mprashad, openshift-bugs-escalate, pdwyer, rhowe, sauchter, sjenning, tatanaka, vwalek
Target Milestone: ---   
Target Release: 3.7.z   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1583129 Environment:
Last Closed: 2018-08-09 22:14:04 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:

Comment 4 DeShuai Ma 2018-07-17 09:10:05 UTC
The fix has cause to regression bug https://bugzilla.redhat.com/show_bug.cgi?id=1601378

Comment 10 DeShuai Ma 2018-08-06 09:58:47 UTC
Verify on v3.7.61, no error log "Error creating subnet for node"

[root@dma37-master-etcd-nfs-1 ~]# oc version
oc v3.7.61
kubernetes v1.7.6+a08f5eeb62
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://dma37-master-etcd-nfs-1:8443
openshift v3.7.61
kubernetes v1.7.6+a08f5eeb62
[root@dma37-master-etcd-nfs-1 ~]# oc get node
NAME                           STATUS    AGE       VERSION
dma37-master-etcd-nfs-1        Ready     2h        v1.7.6+a08f5eeb62
dma37-node-registry-router-1   Ready     2h        v1.7.6+a08f5eeb62

Comment 12 errata-xmlrpc 2018-08-09 22:14:04 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-2018:2337