Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A53CF101A8 for ; Tue, 2 Dec 2014 10:20:13 +0000 (UTC) Received: (qmail 22728 invoked by uid 500); 2 Dec 2014 10:20:13 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 22699 invoked by uid 500); 2 Dec 2014 10:20:13 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 22689 invoked by uid 500); 2 Dec 2014 10:20:13 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 22686 invoked by uid 99); 2 Dec 2014 10:20:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Dec 2014 10:20:13 +0000 Date: Tue, 2 Dec 2014 10:20:13 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-7994) Network rules are not configured in VR after out-of-band movement due to host crash MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CLOUDSTACK-7994?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231267#comment-14231267 ] ASF subversion and git services commented on CLOUDSTACK-7994: ------------------------------------------------------------- Commit 8a91aa9afa8f58266393c7c9949893ca4ce18fb7 in cloudstack's branch refs/heads/4.3 from [~koushikd] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8a91aa9 ] CLOUDSTACK-7994: Network rules are not configured in VR after out-of-band movement due to host crash Ensure that VR is re-booted when it is moved to another host out-of-band. This is necessary to re-program all network rules (cherry picked from commit 513adab51b53ba1acdea908225cfffab90ca1595) Signed-off-by: Rohit Yadav Conflicts: server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java > Network rules are not configured in VR after out-of-band movement due to host crash > ----------------------------------------------------------------------------------- > > Key: CLOUDSTACK-7994 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7994 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Management Server, VMware > Affects Versions: 4.4.0, 4.5.0, 4.3.1, 4.4.1, 4.4.2, 4.3.2 > Reporter: Koushik Das > Assignee: Koushik Das > Fix For: 4.5.0, 4.4.3, 4.3.2 > > > This is specific to Vmware. If VR is moved out-of-band from one host to another then the configured network rules are lost. > In order to re-configure VR with the rules it needs to be rebooted. -- This message was sent by Atlassian JIRA (v6.3.4#6332)