openshift / origin

Conformance test suite for OpenShift
http://www.openshift.org
Apache License 2.0
8.48k stars 4.7k forks source link

[k8s.io] InitContainer should not start app containers and fail the pod if init containers fail on a RestartNever pod [Suite:openshift/conformance/parallel] [Suite:k8s] #18595

Closed sosiouxme closed 6 years ago

sosiouxme commented 6 years ago
Command: go run hack/e2e.go -v -test --test_args='--ginkgo.focus=InitContainer\sshould\snot\sstart\sapp\scontainers\sand\sfail\sthe\spod\sif\sinit\scontainers\sfail\son\sa\sRestartNever\spod\s\[Suite\:openshift\/conformance\/parallel\]\s\[Suite\:k8s\]$'
/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/init_container.go:452

Expected
    <*errors.errorString | 0xc421e763b0>: {
        s: "second init container should have reason PodInitializing: v1.ContainerStatus{Name:\"init1\", State:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(0xc4216bd400), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, LastTerminationState:v1.ContainerState{Waiting:(*v1.ContainerStateWaiting)(nil), Running:(*v1.ContainerStateRunning)(nil), Terminated:(*v1.ContainerStateTerminated)(nil)}, Ready:false, RestartCount:0, Image:\"gcr.io/google_containers/busybox:1.24\", ImageID:\"\", ContainerID:\"\"}",
    }
to be nil
/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/init_container.go:436

https://openshift-gce-devel.appspot.com/build/origin-ci-test/pr-logs/pull/openshift_openshift-ansible/7110/test_pull_request_openshift_ansible_extended_conformance_install/5085/

sjenning commented 6 years ago

/assign

openshift-bot commented 6 years ago

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 commented 6 years ago

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 commented 6 years ago

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