[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-8616?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629573#comment-14629573
 ] 

ASF subversion and git services commented on CLOUDSTACK-8616:
-------------------------------------------------------------

Commit b29d8e72801173e7a3d868c7badaefe8872e4736 in cloudstack's branch 
refs/heads/master from [~wilder.rodrigues]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b29d8e7 ]

CLOUDSTACK-8616 - Adding important remark about the use of buildsystemvm.sh

   - For package installation/update please refer to: 
cloud-tools/appliance/definitions/systemvmtemplate/install_systemvm_packages.sh

Signed-off-by: wilderrodrigues <wrodrig...@schubergphilis.com>

This closes #587


> Redundant VPC with both routers as Master
> -----------------------------------------
>
>                 Key: CLOUDSTACK-8616
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8616
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Virtual Router
>    Affects Versions: 4.6.0
>            Reporter: Wilder Rodrigues
>            Assignee: Wilder Rodrigues
>
> There is an intermittent problem with the keepalived on the redundant VPC 
> routers. Sometimes both routers stay on Master state for a while.
> We are able to reproduce it only when testing with Marvin, which executes the 
> calls very quick. When using the UI and following the same steps, it doesn't 
> happen.
> Setting up:
> 1. Create a VPC using redundant VPC offering
> 2. Add 2 Tiers
> 3. Create 2 VMs in each Tier
> 4. Create ACLs to allow traffic on port 22 coming from 0.0.0.0/0
> 5. Acquire 4 public IPs
> 6. Create Port Forwarding rules - per IP - for port 22
> 7. Assign each PF created to one of the VMs
> 8. SSH to the VMs
> Testing fail over:
> 1. Stop the Master Router
> 2. Check the the Backup Router became Master
> 3. SSH to the VMs 
> Testing failure:
> 1. Delete all port forwarding rules
> 2. SSH to the VMs 
> 3. Verify that it no longer works
> Test recovering
> 1. Restart the router
> 2. Once the router is running, check that it's on Backup state
> 3. Add the port forwarding rules back
> 4. Verify that the routers are still on the same state: 1 Master and 1 Backup
>     - That's the part when it fails during the Marvin tests
>     - When 2 routers are on Master, by restarting 1 router will bring 
> everything to a normal state: 1 master and 1 backup
> 5. SSH to the VMs 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to