Re: [kubernetes/kubernetes] Flaky Tests: [sig-storage] 5000-node correctness tests (#66376)

1 view
Skip to first unread message

Kubernetes Submit Queue

unread,
Jul 19, 2018, 6:35:12 AM7/19/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

[MILESTONENOTIFIER] Milestone Issue Needs Approval

@shyamjvs @kubernetes/sig-storage-misc

Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 4 days, the issue will be moved out of the v1.12 milestone.

Issue Labels
  • sig/storage: Issue will be escalated to these SIGs if needed.
  • priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.
  • kind/bug: Fixes a bug discovered during the current release.
Help


You are receiving this because you are on a team that was mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Michelle Au

unread,
Jul 19, 2018, 11:34:35 AM7/19/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Volume expansion tests have been fixed by #66324

Michelle Au

unread,
Jul 19, 2018, 11:39:44 AM7/19/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

/assign @davidz627
can you investigate the remaining failures?

Kubernetes Submit Queue

unread,
Jul 19, 2018, 11:40:41 AM7/19/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

[MILESTONENOTIFIER] Milestone Issue Needs Approval

@davidz627 @shyamjvs @kubernetes/sig-storage-misc

Action required: This issue must have the status/approved-for-milestone label applied by a SIG maintainer. If the label is not applied within 4 days, the issue will be moved out of the v1.12 milestone.

Issue Labels
  • sig/storage: Issue will be escalated to these SIGs if needed.
  • priority/important-soon: Escalate to the issue owners and SIG owner; move out of milestone after several unsuccessful escalation attempts.
  • kind/bug: Fixes a bug discovered during the current release.
Help

Kubernetes Submit Queue

unread,
Jul 20, 2018, 7:03:12 PM7/20/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Closed #66376 via #66405.

Shyam JVS

unread,
Aug 16, 2018, 5:26:04 AM8/16/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Reopening this issue, as a bunch of storage-related e2es started flaking in our large-scale jobs recently:

/reopen

k8s-ci-robot

unread,
Aug 16, 2018, 5:26:40 AM8/16/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

Reopened #66376.

Michelle Au

unread,
Aug 16, 2018, 9:50:55 AM8/16/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

I think the latest failures are caused by gce API rate limiting: #67348

/assign @bowei @jingax10

Michelle Au

unread,
Aug 16, 2018, 10:04:43 AM8/16/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

It seems to only be failing on scalability test suites. I wonder if it's due to some different cidr configuration

Tim Pepper

unread,
Aug 20, 2018, 1:14:26 PM8/20/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

/sig scalability

guineveresaenger

unread,
Aug 20, 2018, 1:15:05 PM8/20/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

/kind failing-test

Shyam JVS

unread,
Aug 27, 2018, 5:39:33 AM8/27/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

/status approved-for-milestone

Friendly ping. This is affecting release-blocking scalability job.

Davanum Srinivas

unread,
Aug 27, 2018, 7:56:48 AM8/27/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

hey @shyamjvs what needs to be done here? by whom?

Shyam JVS

unread,
Aug 27, 2018, 10:01:20 AM8/27/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

@michelle192837 Could you comment on what needs to be done here and by whom?

Michelle Au

unread,
Aug 27, 2018, 10:26:09 AM8/27/18
to kubernetes/kubernetes, k8s-mirror-storage-misc, Team mention

@bowei @jingax10 can you guys take a look at the API quota issue? This is happening consistently in the scale test environment

Reply all
Reply to author
Forward
0 new messages