While investigating our broken ci I came across consistent messages of 259 times in one log:
```
I0513 14:43:10.700698       1 event.go:278] Event(v1.ObjectReference{Kind:"Deployment", Namespace:"openshift-etcd-operator", Name:"etcd-operator", UID:"bed768d5-a918-42a9-a836-096fa5f511be", APIVersion:"apps/v1", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'UnhealthyEtcdMember' unhealthy members: etcd-bootstrap,ci-op-wmnxm-m-0.c.openshift-gce-devel-ci.internal
```

In our failed runs:
https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1728/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2214/artifacts/e2e-gcp-op/pods/openshift-etcd-operator_etcd-operator-647b7c8bf-t577d_operator.log

(from https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1728/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2214/artifacts/e2e-gcp-op/pods/)

Another example:

https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1724/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2215/artifacts/e2e-gcp-op/pods/openshift-etcd-operator_etcd-operator-5759786ffc-4ncd2_operator.log

(from https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1724/pull-ci-openshift-machine-config-operator-master-e2e-gcp-op/2215/artifacts/e2e-gcp-op/pods/)

However looking at out passing runs we don't even have logs for openshift-etcd-operator in the list of pods? (https://gcsweb-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1727/pull-ci-openshift-machine-config-operator-release-4.2-e2e-gcp-op/80/artifacts/e2e-gcp-op/pods/)

Is something causing this? Why would the member be unhealthy? Is this networking related?