[
https://issues.apache.org/jira/browse/CLOUDSTACK-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15301371#comment-15301371
]
ASF subversion and git services commented on CLOUDSTACK-6975:
-------------------------------------------------------------
Commit 5ccebf0f2b10d1cbc0a97f441e0c00646d84fcad in cloudstack's branch
refs/heads/4.8 from [[email protected]]
[ 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 <[email protected]>
> 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)
