At the moment, the "init_host" method initializes the distributed
lock mechanism, yet the driver may try to use distributed locks
before that.
For example, the method that reclaims failed over instances is
called by the driver init method, before init_host. While we
can fix this particular call, it's safer that we initialize the
lock mechanism as early as possible.
Reviewed: https:/ /review. opendev. org/679726 /git.openstack. org/cgit/ openstack/ compute- hyperv/ commit/ ?id=20c1b2083f4 e684f731d1e0593 024b4685dedd7d
Committed: https:/
Submitter: Zuul
Branch: master
commit 20c1b2083f4e684 f731d1e0593024b 4685dedd7d
Author: Lucian Petrut <email address hidden>
Date: Tue Sep 3 11:22:14 2019 +0300
Initialize coordination during driver init
At the moment, the "init_host" method initializes the distributed
lock mechanism, yet the driver may try to use distributed locks
before that.
For example, the method that reclaims failed over instances is
called by the driver init method, before init_host. While we
can fix this particular call, it's safer that we initialize the
lock mechanism as early as possible.
Change-Id: If361c0f754d368 0726762e3126286 227bea6f3f3
Related-Bug: #1841777