ResultFAILURE
Tests 7 failed / 913 succeeded
Started2019-11-07 17:39
Elapsed3h20m
Work namespaceci-op-xqmwvvj3
pod4.3.0-0.nightly-2019-11-07-172437-aws-fips

Test Failures


openshift-tests Monitor cluster while tests execute 28m39s

go run hack/e2e.go -v -test --test_args='--ginkgo.focus=openshift\-tests\sMonitor\scluster\swhile\stests\sexecute$'
1 error level events were detected during this test run:

Nov 07 20:24:57.750 E ns/default pod/recycler-for-nfs-7gdh9 node/ip-10-0-138-219.ec2.internal pod failed (DeadlineExceeded): Pod was active on the node longer than the specified deadline

				
				Click to see stdout/stderrfrom junit_e2e_20191107-204610.xml

Find failed mentions in log files


openshift-tests [Feature:Platform] Managed cluster should have no crashlooping pods in core namespaces over two minutes [Suite:openshift/conformance/parallel] 2m3s

go run hack/e2e.go -v -test --test_args='--ginkgo.focus=openshift\-tests\s\[Feature\:Platform\]\sManaged\scluster\sshould\shave\sno\scrashlooping\spods\sin\score\snamespaces\sover\stwo\sminutes\s\[Suite\:openshift\/conformance\/parallel\]$'
fail [github.com/openshift/origin/test/extended/operators/cluster.go:122]: Expected
    <[]string | len:1, cap:1>: [
        "Pod openshift-machine-config-operator/etcd-quorum-guard-cd87b6bd-922pq was pending entire time: unknown error",
    ]
to be empty
				
				Click to see stdout/stderrfrom junit_e2e_20191107-204610.xml

Filter through log files


openshift-tests [Feature:Platform][Smoke] Managed cluster should start all core operators [Suite:openshift/conformance/parallel] 1m3s

go run hack/e2e.go -v -test --test_args='--ginkgo.focus=openshift\-tests\s\[Feature\:Platform\]\[Smoke\]\sManaged\scluster\sshould\sstart\sall\score\soperators\s\[Suite\:openshift\/conformance\/parallel\]$'
fail [github.com/openshift/origin/test/extended/operators/operators.go:160]: Nov  7 20:11:49.505: Some cluster operators never became available /machine-config
				
				Click to see stdout/stderrfrom junit_e2e_20191107-204610.xml

Filter through log files


openshift-tests [Feature:Prometheus][Conformance] Prometheus when installed on the cluster shouldn't have failing rules evaluation [Suite:openshift/conformance/parallel/minimal] 7m17s

go run hack/e2e.go -v -test --test_args='--ginkgo.focus=openshift\-tests\s\[Feature\:Prometheus\]\[Conformance\]\sPrometheus\swhen\sinstalled\son\sthe\scluster\sshouldn\'t\shave\sfailing\srules\sevaluation\s\[Suite\:openshift\/conformance\/parallel\/minimal\]$'
fail [github.com/openshift/origin/test/extended/prometheus/prometheus_builds.go:134]: Expected
    <map[string]error | len:1>: {
        "prometheus_rule_evaluation_failures_total >= 1": {
            s: "promQL query: prometheus_rule_evaluation_failures_total >= 1 had reported incorrect results: prometheus_rule_evaluation_failures_total{endpoint=\"web\", instance=\"10.128.2.8:9091\", job=\"prometheus-k8s\", namespace=\"openshift-monitoring\", pod=\"prometheus-k8s-1\", service=\"prometheus-k8s\"} => 100 @[1573158469.913]\nprometheus_rule_evaluation_failures_total{endpoint=\"web\", instance=\"10.131.0.11:9091\", job=\"prometheus-k8s\", namespace=\"openshift-monitoring\", pod=\"prometheus-k8s-0\", service=\"prometheus-k8s\"} => 110 @[1573158469.913]",
        },
    }
to be empty