{"action":"created","issue":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/64450","repository_url":"https://api.github.com/repos/kubernetes/kubernetes","labels_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/64450/labels{/name}","comments_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/64450/comments","events_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/64450/events","html_url":"https://github.com/kubernetes/kubernetes/issues/64450","id":327335598,"number":64450,"title":"Flaky sig-cli conformance test","user":{"login":"fturib","id":19315664,"avatar_url":"https://avatars1.githubusercontent.com/u/19315664?v=4","gravatar_id":"","url":"https://api.github.com/users/fturib","html_url":"https://github.com/fturib","followers_url":"https://api.github.com/users/fturib/followers","following_url":"https://api.github.com/users/fturib/following{/other_user}","gists_url":"https://api.github.com/users/fturib/gists{/gist_id}","starred_url":"https://api.github.com/users/fturib/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/fturib/subscriptions","organizations_url":"https://api.github.com/users/fturib/orgs","repos_url":"https://api.github.com/users/fturib/repos","events_url":"https://api.github.com/users/fturib/events{/privacy}","received_events_url":"https://api.github.com/users/fturib/received_events","type":"User","site_admin":false},"labels":[{"id":105146071,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/kind/bug","name":"kind/bug","color":"e11d21","default":false},{"id":617149945,"url":"https://api.github.com/repos/kubernetes/kubernetes/labels/needs-sig","name":"needs-sig","color":"ededed","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-29T14:03:57Z","updated_at":"2018-05-29T14:03:58Z","closed_at":null,"author_association":"NONE","body":"**Is this a BUG REPORT or FEATURE REQUEST?**:\r\n/kind bug\r\n\r\n**What happened**:\r\nSome of the sig-cli Conformance tests are flaky (since several weeks) on those test suites:\r\n- kubeadm deployment on GCE\r\n- whatever the network defined (flannel, ipvs, etc ...)\r\n(see [sig-network-gce test grid](http://k8s-testgrid.appspot.com/sig-network-gce#kubeadm-gce-ipvs))\r\n\r\nthese tests are also flaking (but with much lower rate) on version 1.10 and not seems stable on 1.9 (see [sig-cluster-lifecycle-all test grid](http://k8s-testgrid.appspot.com/sig-cluster-lifecycle-all#kubeadm-gce-1.10))\r\n\r\nThe flay tests are:\r\n- [sig-cli] Kubectl client [k8s.io] Update Demo should scale a replication controller [Conformance] 30s\r\n- [sig-cli] Kubectl client [k8s.io] Kubectl run rc should create an rc from an image [Conformance]\r\n- [sig-cli] Kubectl client [k8s.io] Kubectl rolling-update should support rolling-update to same image [Conformance]\r\n- [sig-cli] Kubectl client [k8s.io] Kubectl run --rm job should create a job from an image, then delete the job [Conformance] 18s\r\n\r\n**What you expected to happen**:\r\nThese tests should either be fixed, either flagged as \"flaky\" (and unflagged as \"Conformance\") \r\n\r\n**How to reproduce it (as minimally and precisely as possible)**:\r\nLook into corresponding test grid results.\r\n\r\n**Environment:\r\nI am looking at the Grid tests, as of today : Mon May 29th 2018. \r\n\r\n"},"comment":{"url":"https://api.github.com/repos/kubernetes/kubernetes/issues/comments/392788624","html_url":"https://github.com/kubernetes/kubernetes/issues/64450#issuecomment-392788624","issue_url":"https://api.github.com/repos/kubernetes/kubernetes/issues/64450","id":392788624,"user":{"login":"k8s-ci-robot","id":20407524,"avatar_url":"https://avatars0.githubusercontent.com/u/20407524?v=4","gravatar_id":"","url":"https://api.github.com/users/k8s-ci-robot","html_url":"https://github.com/k8s-ci-robot","followers_url":"https://api.github.com/users/k8s-ci-robot/followers","following_url":"https://api.github.com/users/k8s-ci-robot/following{/other_user}","gists_url":"https://api.github.com/users/k8s-ci-robot/gists{/gist_id}","starred_url":"https://api.github.com/users/k8s-ci-robot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/k8s-ci-robot/subscriptions","organizations_url":"https://api.github.com/users/k8s-ci-robot/orgs","repos_url":"https://api.github.com/users/k8s-ci-robot/repos","events_url":"https://api.github.com/users/k8s-ci-robot/events{/privacy}","received_events_url":"https://api.github.com/users/k8s-ci-robot/received_events","type":"User","site_admin":false},"created_at":"2018-05-29T14:03:58Z","updated_at":"2018-05-29T14:03:58Z","author_association":"COLLABORATOR","body":"@fturib: There are no sig labels on this issue. Please add a sig label.\n\n<details>\n\nA sig label can be added by either:\n\n1. mentioning a sig: `@kubernetes/sig-<group-name>-<group-suffix>`\n    e.g., `@kubernetes/sig-contributor-experience-<group-suffix>` to notify the contributor experience sig, OR\n\n2. specifying the label manually: `/sig <group-name>`\n    e.g., `/sig scalability` to apply the `sig/scalability` label\n\nNote: Method 1 will trigger an email to the group. See the [group list](https://git.k8s.io/community/sig-list.md).\nThe `<group-suffix>` in method 1 has to be replaced with one of these: _**bugs, feature-requests, pr-reviews, test-failures, proposals**_\n\nInstructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md).  If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.\n</details>"}}
{"actor":{"display_login":"k8s-ci-robot"}}