server: fix public IP association/disassociation to new network#3489
Conversation
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
@blueorangutan package |
|
@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✖centos7 ✖debian. JID-124 |
Signed-off-by: Abhishek Kumar <abhishek.mrt22@gmail.com>
|
@blueorangutan package |
|
@shwstppr a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-125 |
|
ping for review @rhtyd @anuragaw @borisroman @nvazquez @DaanHoogland |
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-155)
|
|
Tests lgtm |
|
Looks like this should fix the issues we had earlier, so LGTM! |
Description
Fixes #3321
This changes removes exception throwing while associating an IP address to a new isolated network which is in
Allocatedstate. And it allows disassociating an IP address when it is used for source NAT purpose but network is in allocated state.Refer, #3321 (comment)
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Using cmk,