Network connectivity flake during GCE installation

[smarterclayton]

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/17161/test_pull_request_origin_extended_conformance_gce/10903/

This error looks new since switching to bootstrapping - the network was temporarily unavailable after the API had been reported successfully up (and other actions ran?). At this point in the install there are no nodes active (waiting for bootstrapping) so it seems unlikely this is related to the openshift-sdn component on the master. Unfortunately we don't have master logs from the install portion yet on GCE.

TASK [openshift_hosted : Create default projects] ******************************
Saturday 04 November 2017  20:29:25 +0000 (0:00:07.580)       0:16:35.031 ***** 
changed: [ci-prtest-5a37c28-10903-ig-m-bx69] => (item={'key': u'default', 'value': {u'default_node_selector': u''}})
failed: [ci-prtest-5a37c28-10903-ig-m-bx69] (item={'key': u'logging', 'value': {u'default_node_selector': u''}}) => {"changed": false, "failed": true, "item": {"key": "logging", "value": {"default_node_selector": ""}}, "msg": {"cmd": "/bin/oc adm new-project logging --admin-role=admin --node-selector=", "results": {}, "returncode": 1, "stderr": "The connection to the server internal-api.prtest-5a37c28-10903.origin-ci-int-gce.dev.rhcloud.com:8443 was refused - did you specify the right host or port?\n", "stdout": ""}}
failed: [ci-prtest-5a37c28-10903-ig-m-bx69] (item={'key': u'openshift-infra', 'value': {u'default_node_selector': u''}}) => {"changed": false, "failed": true, "item": {"key": "openshift-infra", "value": {"default_node_selector": ""}}, "msg": {"cmd": "/bin/oc adm new-project openshift-infra --admin-role=admin --node-selector=", "results": {}, "returncode": 1, "stderr": "The connection to the server internal-api.prtest-5a37c28-10903.origin-ci-int-gce.dev.rhcloud.com:8443 was refused - did you specify the right host or port?\n", "stdout": ""}}

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close