os-win doesn't wait for cluster service

[Lucian Petrut]

After a reboot, the Failover Cluster service may be unavailable for a minute. Even if 'clussvc' is started, we may fail to connect to the WMI provider, getting this error: "The remote server has been paused or is in the process of being started". This only came up on WS 2019.

It would make sense for os-win to transparently wait for the cluster service to become available, having a configurable timeout.

[Lucian Petrut (petrutlucian94)]

Fix: https://review.opendev.org/#/c/679014/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/679014
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=b6ce9b33ddaa7a1ab5df09fba775c4a5462feae1
Submitter: Zuul
Branch: master

commit b6ce9b33ddaa7a1ab5df09fba775c4a5462feae1
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 11:34:54 2019 +0300

    Wait for cluster node to be available

    After a reboot, the Failover Cluster WMI provider may be unavailable.
    This change will wait for it when initializing clusterutils, having
    a configurable timeout defaulting to infinite.

    Closes-Bug: #1841779

    Change-Id: Id7f2d65cb0307bc952f1e6a2724295ea524835f3

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/train
Review: https://review.opendev.org/682333

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/682334

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/682333
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=c5450ed0b5842b959ef0a42adf7a0d9d63db23dc
Submitter: Zuul
Branch: stable/train

commit c5450ed0b5842b959ef0a42adf7a0d9d63db23dc
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 11:34:54 2019 +0300

    Wait for cluster node to be available

    After a reboot, the Failover Cluster WMI provider may be unavailable.
    This change will wait for it when initializing clusterutils, having
    a configurable timeout defaulting to infinite.

    Closes-Bug: #1841779

    Change-Id: Id7f2d65cb0307bc952f1e6a2724295ea524835f3
    (cherry picked from commit b6ce9b33ddaa7a1ab5df09fba775c4a5462feae1)

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/682334
Committed: https://git.openstack.org/cgit/openstack/os-win/commit/?id=027749c401a73f4561d8542cdcaf5672ac9f4ee2
Submitter: Zuul
Branch: stable/stein

commit 027749c401a73f4561d8542cdcaf5672ac9f4ee2
Author: Lucian Petrut <email address hidden>
Date: Wed Aug 28 11:34:54 2019 +0300

    Wait for cluster node to be available

    After a reboot, the Failover Cluster WMI provider may be unavailable.
    This change will wait for it when initializing clusterutils, having
    a configurable timeout defaulting to infinite.

    Closes-Bug: #1841779

    Change-Id: Id7f2d65cb0307bc952f1e6a2724295ea524835f3
    (cherry picked from commit b6ce9b33ddaa7a1ab5df09fba775c4a5462feae1)

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-win 4.3.2 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-win 4.2.1 release.

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/os-win 5.0.0 release.