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
A proper way of picking available FloatingIP #12300
A proper way of picking available FloatingIP #12300
Conversation
Neither vm and network port has to be associated. There are FloatingIps associated only to NetworkPort, these were offered in provisioning dialog and failed.
@miq-bot assign @blomquisg |
@blomquisg should be euwe yes, I'll ask for BZ |
Checked commit Ladas@5da9967 with ruby 2.2.5, rubocop 0.37.2, and haml-lint 0.16.1 |
@miq-bot remove_tag bugzilla_needed |
@blomquisg BZ added |
@Ladas unrecognized command 'remove_tag', ignoring... Accepted commands are: add_label, remove_label, rm_label, assign, set_milestone |
@miq-bot remove_label bugzilla_needed |
@Ladas Cannot remove the following label because they are not recognized: bugzilla_needed |
…floating_ip A proper way of picking available FloatingIP (cherry picked from commit 49d6bdf) https://bugzilla.redhat.com/show_bug.cgi?id=1390203
Euwe Backport details: $ git log -1
commit c7ff12bd056f5664537cad2c357a611e4e45a31d
Author: Greg Blomquist <blomquisg@gmail.com>
Date: Wed Nov 2 18:07:34 2016 -0400
Merge pull request #12300 from Ladas/proper_way_of_picking_available_floating_ip
A proper way of picking available FloatingIP
(cherry picked from commit 49d6bdf0fe8bf26dd65f2529df73e89ded2fb5ce)
https://bugzilla.redhat.com/show_bug.cgi?id=1390203 |
Neither vm and network port has to be associated. There are
FloatingIps associated only to NetworkPort, these were offered
in provisioning dialog and failed.
Steps for Testing/QA [Optional]
During provisioning (AWS) only real available FloatingIps should be offered
Fixes BZ:
https://bugzilla.redhat.com/show_bug.cgi?id=1390203