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

Volume restored from snapshot is not ready for use after provisioning #482

Closed
msau42 opened this issue Mar 4, 2020 · 7 comments
Closed

Volume restored from snapshot is not ready for use after provisioning #482

msau42 opened this issue Mar 4, 2020 · 7 comments
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@msau42
Copy link
Contributor

msau42 commented Mar 4, 2020

E2E flakes saw this error during attach:

I0303 02:40:32.854820       1 csi_handler.go:222] Error processing "csi-1683f88fb840d9231ef604066b4ad499db02dd397e96aab70497b0331f73af8e": failed to attach: rpc error: code = Internal desc = unknown Attach error: failed cloud service attach disk call: googleapi: Error 400: The resource 'projects/k8s-gce-serial-1-5/zones/us-west1-b/disks/pvc-25bf62e1-6739-4e79-87a1-3b575faa4daf' is not ready, resourceNotReady

Ref: kubernetes/kubernetes#88762 (comment)
@msau42
Copy link
Contributor Author

msau42 commented Mar 4, 2020

/kind failing-test

cc @yosmat

@k8s-ci-robot k8s-ci-robot added the kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. label Mar 4, 2020
@msau42 msau42 mentioned this issue Mar 4, 2020
Closed
@jsafrane
Copy link
Contributor

jsafrane commented Mar 5, 2020

It happened during attach of a volume restored from a snapshot. CreateVolume() returned something that was not attachable for ~4 minutes.

@msau42
Copy link
Contributor Author

msau42 commented Mar 17, 2020

cc @yoesmat @yuxiangqian

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jun 15, 2020
@saikat-royc
Copy link
Member

This issue is also tracked in #526. Will be fixed by PR: #527. @msau42 we can close this issue as duplicate.

@msau42
Copy link
Contributor Author

msau42 commented Jun 17, 2020

/close

@k8s-ci-robot
Copy link
Contributor

@msau42: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@arianitu arianitu mentioned this issue Jan 14, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jsafrane @k8s-ci-robot @msau42 @fejta-bot @saikat-royc