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] Projected should be consumable from pods in volume with mappings [Conformance] [Suite:openshift/conformance/parallel] [Suite:k8s] 19s #17879

Closed
deads2k opened this issue Dec 19, 2017 · 3 comments
Assignees
Labels
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

@deads2k
Copy link
Contributor

deads2k commented Dec 19, 2017

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

[sig-storage] Projected should be consumable from pods in volume with mappings [Conformance] [Suite:openshift/conformance/parallel] [Suite:k8s] 19s

/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 | 0xc42044cd90>: {
        s: "failed to get logs from pod-projected-secrets-c6bbb635-e4d4-11e7-93bb-0ee94d15cd78 for projected-secret-volume-test: an error on the server (\"unknown\") has prevented the request from succeeding (get pods pod-projected-secrets-c6bbb635-e4d4-11e7-93bb-0ee94d15cd78)",
    }
    failed to get logs from pod-projected-secrets-c6bbb635-e4d4-11e7-93bb-0ee94d15cd78 for projected-secret-volume-test: an error on the server ("unknown") has prevented the request from succeeding (get pods pod-projected-secrets-c6bbb635-e4d4-11e7-93bb-0ee94d15cd78)
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
@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 3, 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 May 4, 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
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

6 participants