Start all (instead of Disconnected) Site-to-Site VPN connections when VPC VR starts#3863
Merged
Conversation
… VPC VR starts When we restart the VPC after destroying the master VR, the backup VR becomes the master and the site to site connections are not in connected state. The passive VPN connection will be in connected state but the active VPN connection will be in disconnected state
Member
|
@blueorangutan package |
|
@rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress. |
|
Packaging result: ✖centos6 ✔centos7 ✔debian. JID-744 |
Member
|
@blueorangutan test |
|
@rhtyd a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
Trillian test result (tid-888)
|
yadvr
approved these changes
Feb 5, 2020
ustcweizhou
pushed a commit
to ustcweizhou/cloudstack
that referenced
this pull request
Feb 28, 2020
…ache#3863) When we restart the VPC after destroying the master VR, the backup VR becomes the master and the site to site connections are not in the connected state. The passive VPN connection will be in the connected state but the active VPN connection will be in a disconnected state.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
When we restart the VPC after destroying the master VR, the backup VR
becomes the master and the site to site connections are not in
the connected state. The passive VPN connection will be in the connected
state but the active VPN connection will be in a disconnected state
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
Steps to reproduce the issue
1 . Create two VPC's. Configure VPN customer gateway and VPN connection. The steps are clearly explained in here
2 . Once everything is setup properly make sure that the VPN state is "Connected" in both VPC.
3 . Now navigate to "Infrastructure" → "Virtual Routers"
4 . Search for the routers which belong to one of the VPC created above
5 . Now stop the Backup router and eventually destroy it. It is important that you stop/destroy the Backup router and not the Master router
6 . Now navigate to "Networks" → Select "VPC" in the select view drop down menu and select the VPC for which the virtual router has been destroyed.
7 . Now restart the VPC without cleanup. This will create a new backup VR.
8 . Once the backup vr is created, stop/destroy the master router. The steps are similar to destroying the backup router
9 . Again navigate to Networks → vpc and restart the VPC without cleanup. The initial backup router will become the master and a new backup router will be created
10 . Now check the status of the VPN connection
Expected result:
Both the active and passive VPN connections should be in "Connected" state.
Actual result:
Passive VPN was in Connected state and the active VPN was in Disconnected state