You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Chip Childers (JIRA)" <ji...@apache.org> on 2013/04/01 21:17:15 UTC
[jira] [Resolved] (CLOUDSTACK-1827) Redundant router - When VR
Master was stopped failover to VR Backup did not occur
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chip Childers resolved CLOUDSTACK-1827.
---------------------------------------
Resolution: Fixed
please re-test. This was pushed to 4.1.
> Redundant router - When VR Master was stopped failover to VR Backup did not occur
> ---------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1827
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1827
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: MS ASF 4.1 cloudstack 3/27/2013 latest build
> host XEN 6.0.2
> Reporter: angeline shen
> Assignee: Sheng Yang
> Priority: Critical
> Fix For: 4.1.0
>
> Attachments: management-server.log.2013-03-27.gz, Screenshot-CloudStack - Mozilla Firefox-1.png, Screenshot-CloudStack - Mozilla Firefox-2.png, Screenshot-CloudStack - Mozilla Firefox.png
>
>
> 1. create NW offering isolated with Redundant Virtual Router
> 2. In advance zone, create domain d1, domain admin account d1domain
> 3. login admin, deploy VM with above NW offering with RVR. r-4-VM master r-5-VM backup
> r-4-VM master -> stop -> state remain master <-- no failover
> r-5-VM backup -> remain backup <-- no failover
> 4. login d1domain, deploy VM with above NW offering with RVR. r-12-VM master r-11-VM backup
> r-12-VM master -> stop -> state UNKNOWN
> r-11-VM backup -> master. <-- failover occur
> r-12-VM unknown -> start -> backup
> r-11-VM master -> stop -> remain master < -- no failover
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira