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.

Sign up for GitHub

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

Jump to bottom

Extended.[k8s.io] ConfigMap should be consumable in multiple volumes in the same pod [Conformance] [Volume] #14128

Closed
bparees opened this issue May 10, 2017 · 4 comments
Closed

Extended.[k8s.io] ConfigMap should be consumable in multiple volumes in the same pod [Conformance] [Volume] #14128

bparees opened this issue May 10, 2017 · 4 comments
Assignees
@childsb @derekwaynecarr
Labels
component/kubernetes 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

Comments

@bparees
Copy link
Contributor

bparees commented May 10, 2017 •
edited
Loading 

/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin71K5zf/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/configmap.go:494
Expected error:
    <*errors.errorString | 0xc421ba5bd0>: {
        s: "expected pod \"pod-configmaps-3710507f-359c-11e7-88c3-0e807d598d20\" success: <nil>",
    }
    expected pod "pod-configmaps-3710507f-359c-11e7-88c3-0e807d598d20" success: <nil>
not to have occurred
/openshifttmp/openshift/build-rpm-release/tito/rpmbuild-origin71K5zf/BUILD/origin-3.6.0/_output/local/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/util.go:2183

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/1312/testReport/junit/(root)/Extended/_k8s_io__ConfigMap_should_be_consumable_in_multiple_volumes_in_the_same_pod__Conformance___Volume_/
@bparees bparees added component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. priority/P1 labels May 10, 2017
@bparees bparees mentioned this issue May 10, 2017
Merged
@derekwaynecarr
Copy link
Member

@childsb -- can a member of your team help out here?

@spadgett spadgett mentioned this issue Jan 29, 2018
Closed
@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 Feb 13, 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

@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 Mar 16, 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
Assignees

@childsb childsb

@derekwaynecarr derekwaynecarr

Labels
component/kubernetes 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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@childsb @openshift-bot @bparees @derekwaynecarr @openshift-ci-robot