Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[sig-storage] ConfigMap should be consumable in multiple volumes in the same pod [Conformance] [Suite:openshift/conformance/parallel] [Suite:k8s] 25s #18329

Closed
spadgett opened this issue Jan 29, 2018 · 4 comments
Assignees
Labels
component/storage kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1 sig/storage

Comments

@spadgett
Copy link
Member

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

/tmp/openshift/build-rpms/rpm/BUILD/origin-3.9.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/framework.go:648
Expected error:
    <*errors.errorString | 0xc420ced040>: {
        s: "expected pod \"pod-configmaps-e80c92e6-038d-11e8-8b88-0e9dc7e68d80\" success: pod \"pod-configmaps-e80c92e6-038d-11e8-8b88-0e9dc7e68d80\" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [configmap-volume-test]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason: Message:}] Message: Reason: HostIP:10.142.0.4 PodIP:172.16.4.45 StartTime:2018-01-27 18:14:25 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:configmap-volume-test State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:ContainerCannotRun,Message:invalid header field value \"oci runtime error: container_linux.go:247: starting container process caused \\\"process_linux.go:258: applying cgroup configuration for process caused \\\\\\\"open /sys/fs/cgroup/pids/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pode80eb590_038d_11e8_9ffa_42010a8e0002.slice/docker-50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21.scope/cgroup.procs: no such file or directory\\\\\\\"\\\"\\n\",StartedAt:2018-01-27 18:14:28 +0000 UTC,FinishedAt:2018-01-27 18:14:28 +0000 UTC,ContainerID:docker://50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:gcr.io/kubernetes-e2e-test-images/mounttest-amd64:1.0 ImageID:docker-pullable://gcr.io/kubernetes-e2e-test-images/mounttest-amd64@sha256:dc4e2dcfbde16249c4662de673295d00778577bc2e2ca7013a1b85d4f47398ca ContainerID:docker://50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21}] QOSClass:BestEffort}",
    }
    expected pod "pod-configmaps-e80c92e6-038d-11e8-8b88-0e9dc7e68d80" success: pod "pod-configmaps-e80c92e6-038d-11e8-8b88-0e9dc7e68d80" failed with status: {Phase:Failed Conditions:[{Type:Initialized Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason: Message:} {Type:Ready Status:False LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason:ContainersNotReady Message:containers with unready status: [configmap-volume-test]} {Type:PodScheduled Status:True LastProbeTime:0001-01-01 00:00:00 +0000 UTC LastTransitionTime:2018-01-27 18:14:25 +0000 UTC Reason: Message:}] Message: Reason: HostIP:10.142.0.4 PodIP:172.16.4.45 StartTime:2018-01-27 18:14:25 +0000 UTC InitContainerStatuses:[] ContainerStatuses:[{Name:configmap-volume-test State:{Waiting:nil Running:nil Terminated:&ContainerStateTerminated{ExitCode:128,Signal:0,Reason:ContainerCannotRun,Message:invalid header field value "oci runtime error: container_linux.go:247: starting container process caused \"process_linux.go:258: applying cgroup configuration for process caused \\\"open /sys/fs/cgroup/pids/kubepods.slice/kubepods-besteffort.slice/kubepods-besteffort-pode80eb590_038d_11e8_9ffa_42010a8e0002.slice/docker-50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21.scope/cgroup.procs: no such file or directory\\\"\"\n",StartedAt:2018-01-27 18:14:28 +0000 UTC,FinishedAt:2018-01-27 18:14:28 +0000 UTC,ContainerID:docker://50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21,}} LastTerminationState:{Waiting:nil Running:nil Terminated:nil} Ready:false RestartCount:0 Image:gcr.io/kubernetes-e2e-test-images/mounttest-amd64:1.0 ImageID:docker-pullable://gcr.io/kubernetes-e2e-test-images/mounttest-amd64@sha256:dc4e2dcfbde16249c4662de673295d00778577bc2e2ca7013a1b85d4f47398ca ContainerID:docker://50cfa4db50199160498f81233389bb69246bc4a8c5a5f6493028ec140e2f2e21}] QOSClass:BestEffort}
not to have occurred
/tmp/openshift/build-rpms/rpm/BUILD/origin-3.9.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:2197

/kind test-flake
/priority p1
/sig storage

Related to #14128 and #18061

@openshift-ci-robot openshift-ci-robot added kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 sig/storage labels Jan 29, 2018
@openshift-bot
Copy link
Contributor

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-ci-robot openshift-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 29, 2018
@openshift-bot
Copy link
Contributor

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

1 similar comment
@openshift-bot
Copy link
Contributor

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-ci-robot openshift-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Jun 28, 2018
@openshift-bot
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/storage kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. priority/P1 sig/storage
Projects
None yet
Development

No branches or pull requests

5 participants