We're using a hardcoded 15 seconds timeout when canceling WMI jobs.
Some jobs may not be cancelable, some may take longer to stop. For
example, Nova instances may end up in error state after attempting
to delete them as this hardcoded timeout gets exceeded.
That being considered, we're now adding a config option for this,
also increasing the default timeout to 2 minutes.
Ideally, Nova should pass a timeout here. Still, by adding a config
option at the os-win level, it's easier to backport this to older
releases, also providing a default for any kind of WMI job.
Change-Id: I797366c40a3a4bb74fe925bd10697f227e22915c
Closes-Bug: #1790890
(cherry picked from commit 11e28563d4ffacfeb1a65b55b5fe792c61e7d0e4)
(cherry picked from commit fc4f6c916ce99d7f6ff9e38eb67fc78915983fa1)
Reviewed: https:/ /review. openstack. org/607866 /git.openstack. org/cgit/ openstack/ os-win/ commit/ ?id=e312c5806da 39a2ac87b24ce57 de0a6d1ca6e52c
Committed: https:/
Submitter: Zuul
Branch: stable/queens
commit e312c5806da39a2 ac87b24ce57de0a 6d1ca6e52c
Author: Lucian Petrut <email address hidden>
Date: Wed Sep 5 17:52:58 2018 +0300
Add wmi job terminate timeout cfg opt
We're using a hardcoded 15 seconds timeout when canceling WMI jobs.
Some jobs may not be cancelable, some may take longer to stop. For
example, Nova instances may end up in error state after attempting
to delete them as this hardcoded timeout gets exceeded.
That being considered, we're now adding a config option for this,
also increasing the default timeout to 2 minutes.
Ideally, Nova should pass a timeout here. Still, by adding a config
option at the os-win level, it's easier to backport this to older
releases, also providing a default for any kind of WMI job.
Change-Id: I797366c40a3a4b b74fe925bd10697 f227e22915c eb1a65b55b5fe79 2c61e7d0e4) f6ff9e38eb67fc7 8915983fa1)
Closes-Bug: #1790890
(cherry picked from commit 11e28563d4ffacf
(cherry picked from commit fc4f6c916ce99d7