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

[k8s.io] Deployment deployment should delete old replica sets {Kubernetes e2e suite} #28339

Closed
k8s-github-robot opened this issue Jul 1, 2016 · 12 comments
Closed

[k8s.io] Deployment deployment should delete old replica sets {Kubernetes e2e suite} #28339

k8s-github-robot opened this issue Jul 1, 2016 · 12 comments
Assignees
@janetkuo
Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Milestone
v1.4

Comments

@k8s-github-robot
Copy link

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/10295/

Failed: [k8s.io] Deployment deployment should delete old replica sets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:67
Expected error:
    <*errors.StatusError | 0xc820d64100>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "the server does not allow access to the requested resource (post deployments.extensions)",
            Reason: "Forbidden",
            Details: {
                Name: "",
                Group: "extensions",
                Kind: "deployments",
                Causes: [
                    {
                        Type: "UnexpectedServerResponse",
                        Message: "Forbidden: \"/apis/extensions/v1beta1/namespaces/e2e-tests-deployment-4mj4p/deployments\"",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 403,
        },
    }
    the server does not allow access to the requested resource (post deployments.extensions)
not to have occurred
@k8s-github-robot k8s-github-robot added priority/backlog Higher priority than priority/awaiting-more-evidence. kind/flake Categorizes issue or PR as related to a flaky test. labels Jul 1, 2016
@pwittrock pwittrock assigned janetkuo and unassigned janetkuo Jul 6, 2016
@k8s-github-robot k8s-github-robot mentioned this issue Jul 13, 2016
Closed
@pwittrock pwittrock assigned janetkuo and unassigned pwittrock Jul 18, 2016
@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke-staging-parallel/5917/

Failed: [k8s.io] Deployment deployment should delete old replica sets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:67
Expected error:
    <*errors.errorString | 0xc820758080>: {
        s: "failed to wait for pods running: [timed out waiting for the condition]",
    }
    failed to wait for pods running: [timed out waiting for the condition]
not to have occurred

This was referenced Jul 20, 2016
Closed
Closed
@Dmitry1987
Copy link
Contributor

Hi, I wanted to report issue that after "deployment update" (I change image name with "kubectl set image deployment/..... ", and it does rolling update with creating a new replica-set) old replica-set that now has 0 pods, still exist in dashboard. But I guess this ticket addresses it already, right?

@k8s-github-robot
Copy link
Author

https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/kubernetes-e2e-gke/13392/

Failed: [k8s.io] Deployment deployment should delete old replica sets {Kubernetes e2e suite}

/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:67
Expected error:
    <*errors.StatusError | 0xc820cf2180>: {
        ErrStatus: {
            TypeMeta: {Kind: "", APIVersion: ""},
            ListMeta: {SelfLink: "", ResourceVersion: ""},
            Status: "Failure",
            Message: "an error on the server has prevented the request from succeeding (get replicasets.extensions)",
            Reason: "InternalError",
            Details: {
                Name: "",
                Group: "extensions",
                Kind: "replicasets",
                Causes: [
                    {
                        Type: "UnexpectedServerResponse",
                        Message: "Internal Server Error: \"/apis/extensions/v1beta1/namespaces/e2e-tests-deployment-os4zc/replicasets?labelSelector=name%3Dcleanup-pod\"",
                        Field: "",
                    },
                ],
                RetryAfterSeconds: 0,
            },
            Code: 500,
        },
    }
    an error on the server has prevented the request from succeeding (get replicasets.extensions)
not to have occurred
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/test/e2e/deployment.go:489

This was referenced Aug 23, 2016
Closed
Closed
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @janetkuo

This flaky-test issue would love to have more attention...

1 similar comment
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @janetkuo

This flaky-test issue would love to have more attention...

@k8s-github-robot
Copy link
Author

[FLAKE-PING] @janetkuo

This flaky-test issue would love to have more attention.

@k8s-github-robot k8s-github-robot mentioned this issue Sep 9, 2016
Closed
@k8s-github-robot
Copy link
Author

[FLAKE-PING] @janetkuo

This flaky-test issue would love to have more attention.

@k8s-github-robot k8s-github-robot mentioned this issue Sep 16, 2016
Closed
@davidopp
Copy link
Member

davidopp commented Sep 18, 2016 •
edited
Loading

failing in
https://k8s-testgrid.appspot.com/google-1.3-1.4-upgrade#gce-cvm-1.3-cvm-1.4-upgrade-master
https://k8s-testgrid.appspot.com/google-1.3-1.4-upgrade#gke-cvm-1.3-cvm-1.4-upgrade-master

@davidopp davidopp added this to the v1.4 milestone Sep 18, 2016
@Dmitry1987
Copy link
Contributor

@davidopp so this fix will be released in 1.4? 👍

@0xmichalis
Copy link
Contributor

@Dmitry1987

Hi, I wanted to report issue that after "deployment update" (I change image name with "kubectl set image deployment/..... ", and it does rolling update with creating a new replica-set) old replica-set that now has 0 pods, still exist in dashboard. But I guess this ticket addresses it already, right?

This is not an issue and unrelated to the current test flake issue. If you want to prune older replica sets, use revisionHistoryLimit=0 but note that you won't be able to rollback to an older revision if you ever need to.

@Dmitry1987
Copy link
Contributor

Thanks @Kargakis , i didn't know it's expected behavior. Now it makes sense :)

@janetkuo
Copy link
Member

Should be fixed by #33030

@k8s-github-robot k8s-github-robot mentioned this issue Sep 27, 2016
Closed
This was referenced Dec 29, 2016
Closed
Closed
Closed
This was referenced Jan 6, 2017
Closed
Closed
This was referenced Jan 24, 2017
Closed
Closed
Closed
Closed
This was referenced Feb 2, 2017
Closed
Closed
Closed
Closed
Closed
This was referenced Feb 26, 2017
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Mar 6, 2017
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Mar 14, 2017
Closed
This was referenced Mar 23, 2017
Closed
Closed
Closed
This was referenced Apr 1, 2017
Closed
Closed
Closed
Closed
This was referenced Apr 10, 2017
Closed
Closed
This was referenced Apr 19, 2017
Closed
Closed
@k8s-github-robot k8s-github-robot mentioned this issue Apr 28, 2017
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@janetkuo janetkuo

Labels
kind/flake Categorizes issue or PR as related to a flaky test. priority/backlog Higher priority than priority/awaiting-more-evidence.
Projects
None yet
Milestone
v1.4
Development

No branches or pull requests
6 participants
@0xmichalis @janetkuo @pwittrock @davidopp @Dmitry1987 @k8s-github-robot