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

Extended.[k8s.io] Variable Expansion should allow composing env vars into new env vars [Conformance] #13770

Closed
0xmichalis opened this issue Apr 14, 2017 · 1 comment
Assignees
Labels
component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2

Comments

@0xmichalis
Copy link
Contributor

/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/common/expansion.go:70
Error creating Pod
Expected error:
    <*errors.StatusError | 0xc4202d7d80>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "No API token found for service account \"default\", retry after the token is automatically created and added to the service account",
            Reason: "ServerTimeout",
            Details: {
                Name: "create pod",
                Group: "",
                Kind: "serviceaccounts",
                Causes: nil,
                RetryAfterSeconds: 1,
            },
            Code: 500,
        },
    }
    No API token found for service account "default", retry after the token is automatically created and added to the service account
not to have occurred
/go/src/github.com/openshift/origin/vendor/k8s.io/kubernetes/test/e2e/framework/pods.go:60

https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/742/testReport/junit/(root)/Extended/_k8s_io__Variable_Expansion_should_allow_composing_env_vars_into_new_env_vars__Conformance_/

@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 10, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/kubernetes kind/test-flake Categorizes issue or PR as related to test flakes. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. priority/P2
Projects
None yet
Development

No branches or pull requests

4 participants