-
Notifications
You must be signed in to change notification settings - Fork 60
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
Only create new Public IP if one cannot be found #195
Conversation
Looks good @djberg96 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
as mentioned inline, looks like a spec can be added for this.
@bronaghs I think I would have to create a new spec file, since |
I am wondering if you can update |
@bronaghs well, i'm not really testing the overall provisioning, just the method itself. Creating a separate spec file for cloning.rb would probably boost our coverage a bit, too. |
Initial commit. Add initial create_nic spec and suppupporting code. Added more specs for create_nic.
Checked commit https://github.com/djberg96/manageiq-providers-azure/commit/ac78d353f62fbb8d8ec615484854773ddf77f972 with ruby 2.3.3, rubocop 0.52.0, haml-lint 0.20.0, and yamllint 1.10.0 |
@bronaghs I've added some specs. I created a separate |
|
Nevermind, set tag. |
gaprindashvili is 5.9! |
Only create new Public IP if one cannot be found (cherry picked from commit d4ac3bf) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1566577
Gaprindashvili backport details:
|
At the moment, if you select a public IP address when provisioning, but that IP is not currently associated with a NIC, it will create a new IP instead of using the one selected.
This PR modifies the provisioning code so that when a new NIC is provisioned, it will attempt to use the selected public IP before resorting to creating a new one.
Addresses https://bugzilla.redhat.com/show_bug.cgi?id=1531099