[
https://issues.apache.org/jira/browse/CLOUDSTACK-8737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15787379#comment-15787379
]
ASF GitHub Bot commented on CLOUDSTACK-8737:
--------------------------------------------
GitHub user sureshanaparti opened a pull request:
https://github.com/apache/cloudstack/pull/1882
CLOUDSTACK-8737: Removed the missed out-of-band VR reboot code, not
required based on persistent VR changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack
CLOUDSTACK-8737_CodeCleanup
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1882.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 #1882
----
commit bda20dec181b490fc0d2e0712fb72fb0608699df
Author: Suresh Kumar Anaparti <[email protected]>
Date: 2016-12-30T10:08:08Z
CLOUDSTACK-8737: Removed the missed out-of-band VR reboot code, not
required based on persistent VR changes.
----
> Remove out-of-band VR reboot code based on persistent VR configuration changes
> ------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8737
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8737
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.6.0
> Reporter: Koushik Das
> Assignee: Koushik Das
> Fix For: 4.6.0
>
>
> VR reboot was required to reprogram rules in case it was stopped and started
> outside of CS. With persistent VR configuration changes (added in 4.6) the
> rules are persisted across a stop-start of VR. So no need to do VR reboot.
> Refer to the following discussion on dev list.
> http://mail-archives.apache.org/mod_mbox/cloudstack-dev/201506.mbox/%[email protected]%3e
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
