Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1595599 - [3.7] Error creating subnet for node - just error message in logs - OCP on Azure
[3.7] Error creating subnet for node - just error message in logs - OCP on Azure
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cloud Compute (Show other bugs)
3.7.0
Unspecified Unspecified
urgent Severity urgent
: ---
: 3.7.z
Assigned To: Jan Chaloupka
DeShuai Ma
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2018-06-27 04:13 EDT by Jan Chaloupka
Modified: 2018-09-06 17:38 EDT (History)
25 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1583129
Environment:
Last Closed: 2018-08-09 18:14:04 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2337 None None None 2018-08-09 18:15 EDT

  None (edit)
Comment 4 DeShuai Ma 2018-07-17 05:10:05 EDT
The fix has cause to regression bug https://bugzilla.redhat.com/show_bug.cgi?id=1601378
Comment 10 DeShuai Ma 2018-08-06 05:58:47 EDT
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 18:14:04 EDT
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

Note You need to log in before you can comment on or make changes to this bug.