[
https://issues.apache.org/jira/browse/CLOUDSTACK-6975?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15253992#comment-15253992
]
ASF GitHub Bot commented on CLOUDSTACK-6975:
--------------------------------------------
Github user swill commented on the pull request:
https://github.com/apache/cloudstack/pull/1509#issuecomment-213442284
Lets close this PR and open it based off the 4.7 branch. @ustcweizhou's
LGTM vote will still count on the new PR. Lets just reference this PR in the
new PR so we remember to count his vote. :)
Basically how this works is as follows:
- The current release is 4.8.
- We support fixes in one release prior the the current release, and those
fixes are put against the main branch, so in this case 4.7. I am not sure of
the release cycle on this branch, but at some point a newer minor release may
be cut from this branch (something like 4.7.2 for example).
- Whenever a fix is made in a previous release, the fix is then forward
merged into the later releases. This is so the commit hash is consistent
between all branches making it easier to understand if a specific fix is in a
specific branch. So if a commit is added to the 4.7 branch, it will be forward
merged to the 4.8 branch, and then forward merged again to master.
- We treat master as the next release and add new features there and make
sure everything is stable for the next release (in this case 4.9).
Does that all make sense? Don't be shy if you have questions. I will do
my best to support you. :)
> 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)
