cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-6975) Service monitoring starts dnsmasq on backup router when using redundant VRs
Date Fri, 06 May 2016 13:35:12 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15274026#comment-15274026
] 

ASF GitHub Bot commented on CLOUDSTACK-6975:
--------------------------------------------

Github user jburwell commented on a diff in the pull request:

    https://github.com/apache/cloudstack/pull/1514#discussion_r62329838
  
    --- Diff: systemvm/patches/debian/config/opt/cloud/bin/cs/CsDhcp.py ---
    @@ -54,7 +54,8 @@ def process(self):
             self.cloud.commit()
     
             # We restart DNSMASQ every time the configure.py is called in order to avoid
lease problems.
    -        CsHelper.service("dnsmasq", "restart")
    +        if not self.cl.is_redundant() or self.cl.is_master():
    --- End diff --
    
    Would is make sense for the ``is_redundant()`` check to be in the ``is_master()`` method?
 To my way of thinking, any non-redundant router is a de facto master.  
    
    I understand such a change may be too far to be practical at this time, so we may want
to table it.


> 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)

Mime
View raw message