[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.
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.—
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.![]()
Volume expansion tests have been fixed by #66324
/assign @davidz627
can you investigate the remaining failures?
[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.
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.—
Reopening this issue, as a bunch of storage-related e2es started flaking in our large-scale jobs recently:
/reopen
Reopened #66376.
It seems to only be failing on scalability test suites. I wonder if it's due to some different cidr configuration
/sig scalability
/kind failing-test
/status approved-for-milestone
Friendly ping. This is affecting release-blocking scalability job.
hey @shyamjvs what needs to be done here? by whom?
@michelle192837 Could you comment on what needs to be done here and by whom?