e2e flake: SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching

[smarterclayton]

Extended.[k8s.io] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching (from (conformance_serial_01.xml))

Failing for the past 1 build (Since Failed#4627 )
Took 20 sec.
add description
Stacktrace

/data/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:1549
Expected error:
    <*errors.StatusError | 0xc820e64600>: {
        ErrStatus: {
            TypeMeta: {Kind: "Status", APIVersion: "v1"},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "Operation cannot be fulfilled on nodes \"172.18.3.206\": the object has been modified; please apply your changes to the latest version and try again",
            Reason: "Conflict",
            Details: {Name: "172.18.3.206", Group: "", Kind: "nodes", Causes: nil, RetryAfterSeconds: 0},
            Code: 409,
        },
    }
    Operation cannot be fulfilled on nodes "172.18.3.206": the object has been modified; please apply your changes to the latest version and try again
not to have occurred

[smarterclayton]

https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin_conformance/4627/

[smarterclayton]

kubernetes/kubernetes#28853

[smarterclayton]

Fixed with kubernetes/kubernetes#29847

[enj]

Possibly seen in https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/158/#showFailuresLink for #13466

Regression

Extended.[k8s.io] SchedulerPredicates [Serial] validates that taints-tolerations is respected if not matching (from (empty))
Failing for the past 1 build (Since Failed#158 )
Took 10 sec.
Stacktrace

/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:100
Expected error:
    <*errors.errorString | 0xc421400d00>: {
        s: "Namespace e2e-tests-emptydir-qjphb is active",
    }
    Namespace e2e-tests-emptydir-qjphb is active
not to have occurred
/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:78

Standard Output

[BeforeEach] [Top Level]
  /go/src/github.com/openshift/origin/test/extended/util/test.go:47
[BeforeEach] [k8s.io] SchedulerPredicates [Serial]
  /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:141
STEP: Creating a kubernetes client
Mar 21 00:41:40.220: INFO: >>> kubeConfig: /etc/origin/master/admin.kubeconfig

STEP: Building a namespace api object
Mar 21 00:41:40.299: INFO: About to run a Kube e2e test, ensuring namespace is privileged
STEP: Waiting for a default service account to be provisioned in namespace
[BeforeEach] [k8s.io] SchedulerPredicates [Serial]
  /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:100
Mar 21 00:41:40.357: INFO: Waiting up to 1m0s for all (but 0) nodes to be ready
Mar 21 00:41:40.360: INFO: Waiting for terminating namespaces to be deleted...
Mar 21 00:41:40.362: INFO: Unexpected error occurred: Namespace e2e-tests-emptydir-qjphb is active
[AfterEach] [k8s.io] SchedulerPredicates [Serial]
  /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:142
STEP: Collecting events from namespace "e2e-tests-sched-pred-6z46l".
STEP: Found 0 events.
Mar 21 00:41:40.368: INFO: POD                       NODE                         PHASE    GRACE  CONDITIONS
Mar 21 00:41:40.368: INFO: docker-registry-1-wrj69   ip-172-18-1-91.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:27 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:33 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:27 -0400 EDT  }]
Mar 21 00:41:40.368: INFO: registry-console-1-clwv9  ip-172-18-1-91.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:32 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:52 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:32 -0400 EDT  }]
Mar 21 00:41:40.368: INFO: router-1-qm5v1            ip-172-18-1-91.ec2.internal  Running         [{Initialized True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:05:44 -0400 EDT  } {Ready True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:06:04 -0400 EDT  } {PodScheduled True 0001-01-01 00:00:00 +0000 UTC 2017-03-21 00:05:44 -0400 EDT  }]
Mar 21 00:41:40.369: INFO: 
Mar 21 00:41:40.370: INFO: 
Logging node info for node ip-172-18-1-91.ec2.internal
Mar 21 00:41:40.372: INFO: Node Info: &TypeMeta{Kind:,APIVersion:,}
Mar 21 00:41:40.372: INFO: 
Logging kubelet events for node ip-172-18-1-91.ec2.internal
Mar 21 00:41:40.374: INFO: 
Logging pods the kubelet thinks is on node ip-172-18-1-91.ec2.internal
Mar 21 00:41:40.378: INFO: router-1-qm5v1 started at 2017-03-21 00:05:44 -0400 EDT (0+1 container statuses recorded)
Mar 21 00:41:40.378: INFO: 	Container router ready: true, restart count 0
Mar 21 00:41:40.378: INFO: docker-registry-1-wrj69 started at 2017-03-21 00:06:27 -0400 EDT (0+1 container statuses recorded)
Mar 21 00:41:40.378: INFO: 	Container registry ready: true, restart count 0
Mar 21 00:41:40.378: INFO: registry-console-1-clwv9 started at 2017-03-21 00:06:32 -0400 EDT (0+1 container statuses recorded)
Mar 21 00:41:40.378: INFO: 	Container registry-console ready: true, restart count 0
Mar 21 00:41:40.476: INFO: 
Latency metrics for node ip-172-18-1-91.ec2.internal
Mar 21 00:41:40.476: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.99 Latency:38.841105s}
Mar 21 00:41:40.476: INFO: {Operation:stop_container Method:docker_operations_latency_microseconds Quantile:0.99 Latency:30.158729s}
Mar 21 00:41:40.476: INFO: {Operation: Method:pod_start_latency_microseconds Quantile:0.9 Latency:25.916558s}
Mar 21 00:41:40.476: INFO: {Operation:SyncPod Method:container_manager_latency_microseconds Quantile:0.99 Latency:11.764217s}
STEP: Dumping a list of prepulled images on each node
Mar 21 00:41:40.478: INFO: Waiting up to 3m0s for all (but 0) nodes to be ready
STEP: Destroying namespace "e2e-tests-sched-pred-6z46l" for this suite.
Mar 21 00:41:50.559: INFO: namespace: e2e-tests-sched-pred-6z46l, resource: bindings, ignored listing per whitelist
[AfterEach] [k8s.io] SchedulerPredicates [Serial]
  /go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/scheduler_predicates.go:67

[ncdc]

This just looks like the namespace took too long to delete, which happens sometimes. Reopen if needed.