Local volume provisioner role workaround for mitogen

[spaced]

workaround for delegate with mitogen

/kind bug

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes

Exception ignored in: <bound method Connection.__del__ of <ansible.plugins.connection.mitogen_ssh.Connection object at 0x7f1d3f4ac278>>
Traceback (most recent call last):
  File "/opt/kubespray/plugins/mitogen/ansible_mitogen/connection.py", line 513, in __del__
    self.close()
  File "/opt/kubespray/plugins/mitogen/ansible_mitogen/connection.py", line 827, in close
    self._put_connection()
  File "/opt/kubespray/plugins/mitogen/ansible_mitogen/connection.py", line 808, in _put_connection
    self.chain.reset()
  File "/opt/kubespray/plugins/mitogen/mitogen/parent.py", line 1846, in reset
    self.call_no_reply(mitogen.core.Dispatcher.forget_chain, saved)
  File "/opt/kubespray/plugins/mitogen/mitogen/parent.py", line 1901, in call_no_reply
    self.context.send(self.make_msg(fn, *args, **kwargs))
  File "/opt/kubespray/plugins/mitogen/mitogen/core.py", line 2272, in send
    self.router.route(msg)
  File "/opt/kubespray/plugins/mitogen/mitogen/core.py", line 3345, in route
    self.broker.defer(self._async_route, msg)
  File "/opt/kubespray/plugins/mitogen/mitogen/core.py", line 2826, in defer
    raise Error(self.broker_shutdown_msg)
mitogen.core.Error: An attempt was made to enqueue a message with a Broker that has already exitted. It is likely your program called Broker.shutdown() too early.
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: mitogen.core.Error: An attempt was made to enqueue a message with a Broker that has already exitted. It is likely your program called Broker.shutdown() too early.
fatal: [mymaster0]: FAILED! => {"msg": "Unexpected failure during module execution.", "stdout": ""}

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

[k8s-ci-robot]

Hi @spaced. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[floryut]

/ok-to-test

[floryut]

/lgtm

[LuckySB]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: LuckySB, spaced

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [LuckySB]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment