Uh oh!
There was an error while loading. Please reload this page.
Ignore site to site vpn status check on internallbvm - #3864
Conversation
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
andrijapanicsb
commented
Feb 7, 2020
@ravening since this is a bug fix, do you mind rebasing against 4.13 so we can merge it there and merge forward to master afterwards? |
yadvr
commented
Feb 12, 2020
@blueorangutan package |
blueorangutan
commented
Feb 12, 2020
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
164f984 to
4630e85Compareblueorangutan
commented
Feb 12, 2020
Packaging result: ✖centos6 ✖centos7 ✔debian. JID-817 |
When the state of the site to site vpn changes, the check is done on all the virtual routers including the internal load balancing vm as well. It is not needed to check the state for internal load balancing vm
4630e85 to
2215f8bCompareravening
commented
Feb 12, 2020
Rebased to 4.13 |
yadvr
commented
Feb 12, 2020
@blueorangutan package |
blueorangutan
commented
Feb 12, 2020
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
blueorangutan
commented
Feb 12, 2020
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-839 |
yadvr
commented
Feb 12, 2020
@blueorangutan test |
blueorangutan
commented
Feb 12, 2020
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
blueorangutan
commented
Feb 12, 2020
Trillian test result (tid-963)
|
yadvr
commented
Feb 12, 2020
@blueorangutan test |
blueorangutan
commented
Feb 12, 2020
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
blueorangutan
commented
Feb 13, 2020
Trillian test result (tid-983)
|
DaanHoogland
commented
Feb 13, 2020
@blueorangutan package |
blueorangutan
commented
Feb 13, 2020
@DaanHoogland a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
blueorangutan
commented
Feb 13, 2020
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-855 |
yadvr
commented
Feb 14, 2020
@blueorangutan package |
blueorangutan
commented
Feb 14, 2020
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
blueorangutan
commented
Feb 14, 2020
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-870 |
yadvr
commented
Feb 17, 2020
@blueorangutan test |
blueorangutan
commented
Feb 17, 2020
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
yadvr
commented
Feb 17, 2020
@blueorangutan test |
blueorangutan
commented
Feb 17, 2020
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
yadvr
commented
Feb 17, 2020
@blueorangutan test |
blueorangutan
commented
Feb 17, 2020
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
blueorangutan
commented
Feb 18, 2020
Trillian test result (tid-1013)
|
yadvr
commented
Feb 18, 2020
I checked some issue at the backend. Considering the test on #3864 (comment) LGTM. |
…3864) When the state of the site to site vpn changes, the check is done on all the virtual routers including the internal load balancing vm as well. It is not needed to check the state for internal load balancing vm
…3864) When the state of the site to site vpn changes, the check is done on all the virtual routers including the internal load balancing vm as well. It is not needed to check the state for internal load balancing vm
…3864) When the state of the site to site vpn changes, the check is done on all the virtual routers including the internal load balancing vm as well. It is not needed to check the state for internal load balancing vm
…3864) When the state of the site to site vpn changes, the check is done on all the virtual routers including the internal load balancing vm as well. It is not needed to check the state for internal load balancing vm
Description
When the state of the site to site vpn changes, the check
is done on all the virtual routers including the internal
load balancing vm as well. It is not needed to check the
state for internal load balancing vm
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Steps to reprodcue the issue
1 . Create two VPC's. Configure VPN customer gateway and VPN connection. The steps are clearly explained here
2 . Now navigate to networks section in main cloudstack ui. In the drop down menu select VPC. Click configure on one of the VPC
3 . Click on "Create Network" and create a tier with "DefaultisolatedNetworkOfferingForVPCNetworksWithInternalLB" network offering
4 . Once the tier is created click on "Internal LB" tab.
5 . In the right side, click on "Add Internal LB" button
6 . Enter the input according to your needs and press OK
7 . Once the Internal LB is created, click on it and select the "Assigned VM's" tab.
8 . Click on "Assign VM's" button and select the VM's which are present in this tier. If none are present then create vm's.
9 . This will create a new type of router "internallb" which can be listed using the cloudmonkey command "list internalloadbalancervms" whose name starts with b-
10 . Change the state of any VPN connection in this VPC and observe the logs for the keyword "Site-to-site Vpn Connection to on router b-<>-VM"
Expected result:
A log mesasge mentioned in the step 10 will be displayed in /var/log/cloudstack/management/management-server.log
Actual result:
The above log should not be displayed.