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

[k8s.io] DisruptionController should update PodDisruptionBudget status {Kubernetes e2e suite} #37176

Closed
k8s-github-robot opened this issue Nov 20, 2016 · 1 comment
Assignees
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Milestone

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-kops-aws/1705/

Failed: [k8s.io] DisruptionController should update PodDisruptionBudget status {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/disruption.go:74
Expected error:
    <*url.Error | 0xc420d12a80>: {
        Op: "Post",
        URL: "https://api.e2e-kops-aws.test-aws.k8s.io/apis/policy/v1beta1/namespaces/e2e-tests-disruption-4bshj/poddisruptionbudgets",
        Err: {
            Op: "dial",
            Net: "tcp",
            Source: nil,
            Addr: {
                IP: [0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 255, 35, 160, 90, 163],
                Port: 443,
                Zone: "",
            },
            Err: {},
        },
    }
    Post https://api.e2e-kops-aws.test-aws.k8s.io/apis/policy/v1beta1/namespaces/e2e-tests-disruption-4bshj/poddisruptionbudgets: dial tcp 35.160.90.163:443: i/o timeout
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/disruption.go:197

Previous issues for this test: #34119

@k8s-github-robot k8s-github-robot added kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. labels Nov 20, 2016
@calebamiles calebamiles added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label Feb 27, 2017
@bsalamat
Copy link
Member

bsalamat commented Mar 8, 2017

This test has been consistently passing in the past couple of weeks. Should we close it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Development

No branches or pull requests

5 participants