Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 0A781200AE4 for ; Thu, 26 May 2016 04:55:18 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 09186160A39; Thu, 26 May 2016 02:55:18 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 5101D160A2E for ; Thu, 26 May 2016 04:55:17 +0200 (CEST) Received: (qmail 35216 invoked by uid 500); 26 May 2016 02:55:14 -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 35035 invoked by uid 500); 26 May 2016 02:55:14 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 34983 invoked by uid 99); 26 May 2016 02:55:14 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 May 2016 02:55:14 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 07C9D2C1F5D for ; Thu, 26 May 2016 02:55:14 +0000 (UTC) Date: Thu, 26 May 2016 02:55:14 +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-6975) Service monitoring starts dnsmasq on backup router when using redundant VRs MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Thu, 26 May 2016 02:55:18 -0000 [ https://issues.apache.org/jira/browse/CLOUDSTACK-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301383#comment-15301383 ] ASF subversion and git services commented on CLOUDSTACK-6975: ------------------------------------------------------------- Commit 5ccebf0f2b10d1cbc0a97f441e0c00646d84fcad in cloudstack's branch refs/heads/master from [~williamstevens@gmail.com] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=5ccebf0 ] Merge pull request #1514 from dsclose/CLOUDSTACK-6975 CLOUDSTACK-6975: Prevent dnsmasq from starting on backup redundant RvRRebase of PR #1509 against the 4.7 branch as requested by @swill One LGTM from @ustcweizhou carried from previous PR. Previous PR will be closed. Description from PR #1509: CLOUDSTACK-6975 refers to service monitoring bringing up dnsmasq but this is no-longer accurate, as service monitoring is not active on the post-4.6 routers. These routers still suffer an essentially identical issue, however, because "dnsmasq needs to be restarted each time configure.py is called in order to avoid lease problems." As such, dnsmasq is still running on backup RvRs, causing the issues described in CLOUDSTACK-6975. This PR is based on a patch submitted by @ustcweizhou. The code now checks the redundant state of the router before restarting dnsmasq. RvR networks without this patch have dnsmasq running on both master and backup routers. RvR networks with this patch have dnsmasq running on only the master router. * pr/1514: CLOUDSTACK-6975: Prevent dnsmasq from starting on backup redundant RvR. Signed-off-by: Will Stevens > Service monitoring starts dnsmasq on backup router when using redundant VRs > --------------------------------------------------------------------------- > > Key: CLOUDSTACK-6975 > URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6975 > Project: CloudStack > Issue Type: Bug > Security Level: Public(Anyone can view this level - this is the default.) > Components: Virtual Router > Affects Versions: 4.3.0 > Environment: KVM > Reporter: Magnus Bengtsson > > When using a network offering with redundant routers the default setting of EnableServiceMonitoring enables monit on the routers. > "network.router.EnableServiceMonitoring service monitoring in router enable/disable option, default true false" > This causes monit to run dnsmasq on both the Master and Backup router. When the backup router assigns dhcp to clients, password and userdata retrieval from that node fails since the services are not running on the backup router. -- This message was sent by Atlassian JIRA (v6.3.4#6332)