GitHub user dsclose reopened a pull request:

    https://github.com/apache/cloudstack/pull/1514

    CLOUDSTACK-6975: Prevent dnsmasq from starting on backup redundant RvR

    Rebase 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.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/dsclose/cloudstack CLOUDSTACK-6975

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/1514.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1514
    
----
commit 38b3bdd488745b3ded6d54ae2d3093842bc4d763
Author: dean.close <dean.cl...@icloudhosting.com>
Date:   2016-05-09T10:34:47Z

    CLOUDSTACK-6975: Prevent dnsmasq from starting on backup redundant RvR.

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

Reply via email to