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.

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

AWS: Volume attachment/detachment requires polling of DescribeVolume #21623

Closed
justinsb opened this issue Feb 20, 2016 · 7 comments
Closed

AWS: Volume attachment/detachment requires polling of DescribeVolume #21623

justinsb opened this issue Feb 20, 2016 · 7 comments
Assignees
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Milestone

Comments

@justinsb
Copy link
Member

See comment here: #12121 (comment)

It would sure be nice to find a way of doing this that doesn't hit our AWS API quota. For example, looking at the disk state. Now that we've harmonized with GCE maybe we can do this.

@justinsb justinsb added this to the next-candidate milestone Feb 20, 2016
@saad-ali saad-ali added team/cluster sig/storage Categorizes an issue or PR as relevant to SIG Storage. labels Mar 2, 2016
@justinsb justinsb modified the milestones: next-candidate, v1.3 Apr 1, 2016
@justinsb
Copy link
Member Author

justinsb commented Jun 3, 2016

It's not great, but we haven't had any problem reports so moving to 1.4

Also there doesn't appear to be an easy way.

@justinsb justinsb modified the milestones: v1.4, v1.3 Jun 3, 2016
@matchstick matchstick added the priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. label Aug 12, 2016
@matchstick
Copy link
Contributor

This might be fixed in 1.3.4 can you try again?

@pwittrock
Copy link
Member

@justinsb I am moving this out of the blocking issues we are tracking for the 1.4 release. If there is still 1.4 work to be done here, move it back and provide daily updates to this issue.

@pwittrock pwittrock modified the milestones: v1.4-nonblocking, v1.4 Sep 8, 2016
@saad-ali
Copy link
Member

saad-ali commented Sep 8, 2016

@justinsb ok with punting this to 1.5?

@justinsb justinsb modified the milestones: v1.5, v1.4-nonblocking Sep 8, 2016
@justinsb
Copy link
Member Author

justinsb commented Sep 8, 2016

Absolutely ... moved to 1.5

@dims
Copy link
Member

dims commented Nov 16, 2016

@justinsb @saad-ali ok with punting this to 1.6? :)

@justinsb
Copy link
Member Author

I actually propose closing, in that it is aspirational. If we observe the problem, we can fix at that time. I think there's actually a separate issue that might have hit it which I re-found in my triage yesterday, in which case we can track there: #31858

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/storage Categorizes an issue or PR as relevant to SIG Storage.
Projects
None yet
Development

No branches or pull requests

7 participants