Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1540606 - [3.7] [OnlineStarter][free-stg][free-int]"Failed create pod sandbox"---deploy failed
[3.7] [OnlineStarter][free-stg][free-int]"Failed create pod sandbox"---deploy...
Status: CLOSED ERRATA
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking (Show other bugs)
3.7.0
Unspecified Unspecified
high Severity high
: ---
: 3.7.z
Assigned To: Ravi Sankar
Meng Bo
: OnlineStarter
Depends On: 1509799 1540608
Blocks: 1512717
  Show dependency treegraph
 
Reported: 2018-01-31 09:10 EST by Ben Bennett
Modified: 2018-04-05 05:37 EDT (History)
30 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: Openshift node was not waiting enough for the VNID as master assigns vnid and it could take a while to propagate to the node. Consequence: Pod creation fails Fix: Increase timeout from 1 to 5 secs for fetching VNID on node. Result: Should allow pod creation to succeed.
Story Points: ---
Clone Of: 1509799
Environment:
Last Closed: 2018-04-05 05:37:08 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 Knowledge Base (Solution) 3337301 None None None 2018-01-31 09:10 EST
Origin (Github) 17243 None None None 2018-01-31 09:10 EST
Github openshift/ose/pull/1044 None None None 2018-02-02 09:12 EST
Red Hat Product Errata RHBA-2018:0636 None None None 2018-04-05 05:37 EDT

  None (edit)
Comment 1 Ravi Sankar 2018-01-31 12:44:05 EST
Fixed by https://github.com/openshift/ose/pull/1044
Comment 3 hongli 2018-02-13 21:08:48 EST
verified in atomic-openshift-3.7.29-1.git.0.0e0f138 and cannot reproduce the issue.
Comment 7 errata-xmlrpc 2018-04-05 05:37:08 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:0636

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