[
https://issues.apache.org/jira/browse/CLOUDSTACK-9709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15782113#comment-15782113
]
ASF GitHub Bot commented on CLOUDSTACK-9709:
--------------------------------------------
GitHub user jayapalu opened a pull request:
https://github.com/apache/cloudstack/pull/1873
CLOUDSTACK-9709: Updated the vm ip fetch task to use the correct the …
Updated the vm ip fetch task to use the seperate thread executor
Also fixed in this
If a vm with iso attached is restarted it would not have the attached iso
after restart.
Detect vmware tools mount status ahead to restore after reboot.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/Accelerite/cloudstack dhcpOffloadFix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1873.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 #1873
----
commit 36658a60d85e6a8926fd1367b138508fefdcb9f1
Author: Jayapal <[email protected]>
Date: 2016-12-27T09:04:28Z
CLOUDSTACK-9709: Updated the vm ip fetch task to use the correct the thread
Also fixed in this
If a vm with iso attached is restarted it would not have the attached iso
after restart.
Detect vmware tools mount status ahead to restore after reboot.
----
> DHCP/DNS offload: Use correct thread pool for IP fetch task
> -----------------------------------------------------------
>
> Key: CLOUDSTACK-9709
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9709
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Network Controller
> Reporter: Jayapal Reddy
> Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> Currently IP fetch task is using the same thread pool as VM expunge. This can
> lead to confusion
> Also the IP fetch task uses another thread pool (name of the variable
> _vmIpFetchThreadExecutor) which is not initialized.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
