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

neutron client needs to change polling strategy #44

Open
richbrowne opened this issue Jun 10, 2016 · 0 comments
Open

neutron client needs to change polling strategy #44

richbrowne opened this issue Jun 10, 2016 · 0 comments

Comments

@richbrowne
Copy link

I don't know why I closed the issue where CLUDS test was failing. But this is a request for change in the testing client.

This issue is likely caused by the way in which the polling client is initialized and implemented. In some cases the .4 second polling interval is too short and causes the api call to happen when the prior one is still in progress. This results in an exception which is not handled by the polling client.

The call to delete should not be retried. In fact, the proper way is to test the existence of the object, and if it exists try to delete, then poll for the existence until it is removed.

So the pattern is:

if x.exists()
x.delete()
while x.exists() and retries < max_retries:
sleep (interval)

if x.exists():
return ERROR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant