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

Fix floating IP assignement #330

Merged
merged 1 commit into from
May 20, 2017
Merged

Fix floating IP assignement #330

merged 1 commit into from
May 20, 2017

Conversation

ggiamarchi
Copy link
Owner

Depending on the latency within Neutron to actually assign the floating IP, the plugin doesn't manage to resolve the IP when it tries to access the machine immediately after the assignment request. A race condition is caused by a missing assignment into the machine config object.

@ggiamarchi ggiamarchi added the bug label May 20, 2017
@ggiamarchi ggiamarchi force-pushed the fix-floatingip branch 2 times, most recently from 605731a to 5c5ffa5 Compare May 20, 2017 18:03
Depending on the latency within Neutron to actually assign the floating
IP, the plugin doesn't manage to resolve the IP when it tries to access the
machine immediately after the assignment request. A race condition is caused
by a missing assignment into the machine config object.
@coveralls
Copy link

coveralls commented May 20, 2017

Coverage Status

Coverage increased (+0.01%) to 87.043% when pulling a7e2af3 on fix-floatingip into 2978da1 on master.

@ggiamarchi ggiamarchi merged commit 53d10aa into master May 20, 2017
@ggiamarchi ggiamarchi deleted the fix-floatingip branch May 20, 2017 20:22
@ggiamarchi ggiamarchi added this to the 0.11.0 milestone May 22, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants