Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Wed, 2 Oct 2013 22:01:43 +0000 (UTC)
From: "Sheng Yang (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12672038.1380751299341.2947.1380751303596@arcas>
In-Reply-To: <JIRA.12672038.1380751299341@arcas>
References: <JIRA.12672038.1380751299341@arcas>
Subject: [jira] [Created] (CLOUDSTACK-4786) Redundant router: the priority
 limitation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Sheng Yang created CLOUDSTACK-4786:
--------------------------------------

             Summary: Redundant router: the priority limitation
                 Key: CLOUDSTACK-4786
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4786
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Network Devices
    Affects Versions: 4.2.0
            Reporter: Sheng Yang
            Assignee: Sheng Yang
             Fix For: 4.2.1


The limitation states that when using RVR, Network GC can run only 40 times or RVR can only be restarted 40 times or Guest VM can only be restart 40 times before having the need to restart the network with cleanup=true (downtime).

Example:
1. Let us say there is one VM in an account/network, VM1.
2. It is using 1 network, say N1 and it's created from a network offering that
has redundant router enabled.
3. When VM1 was launched, two RVRs were created, say R1 and R2.
4. At that time R1 has priority set to 100 and R2 99. This is the default
behavior.
5. Network GC is set to run every 30 minutes.
6. Let us draw a base line here, VM1 is running, R1 is running and has priority set to 100, R2 is running as has priority set to 99.
7. Stop VM1.
8. Wait for 30+ minutes.
9. Check R1 and R2, they will be stopped.
10. Start VM1.
11. R1 and R2 will be started and their priorities will now be set to 99 and 98 resp.
12. If you repeat steps #7 through #10, you will observe that after 40 tries
priorities of R1 and R2 would be 20 and 19. You will observe that the RVR won't start. It will complain about the priority being too low.

The only workaround now is to restart network with cleanup=true, basically
destroy old routers and create new ones.


--
This message was sent by Atlassian JIRA
(v6.1#6144)