fixed inconsistency of IP on VR when VR is destroyed and recrea…#3825
Conversation
|
Regression testing and manual QA against VPC, shared and isolated network with/without redundant router. Also we need to check if L2 is affected (likely not, as there are no routers). |
DaanHoogland
left a comment
There was a problem hiding this comment.
one remark (code itself looks good)
| //return nic only when its ip address belong to the pod range (for the Basic zone case) | ||
| if (vlans.isEmpty()) { | ||
| return nic; | ||
| } |
There was a problem hiding this comment.
I don't think this comment still describves the line below. Can you clarify or remove it?
|
@blueorangutan package |
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✖centos7 ✖debian. JID-653 |
|
@Pearl1594 there is a checkstyle error. Can you check? |
|
@DaanHoogland Handled it |
|
@blueorangutan package |
|
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✔centos6 ✔centos7 ✔debian. JID-655 |
|
@blueorangutan test |
|
@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-818)
|
Description
This address the issue mentioned in #3787 - Guest IP address of Shared Network VR is not persistent when VR is destroyed/recreated
Types of changes
How Has This Been Tested?