Horizon doesn't show down state for vCenter

[okosse]

Step for reproduce:
1. Deploy cluster in Dualhypervisor mode
2. Run a instance via horizon in vcenter availability zone
3. Disconnect vCenter and MOS

Expected result:
Horizon shows status "disabled", state "down" for vcenter hosts
Horizon does not allow to create instances in vcenter availability zone

Actual result:
Horizon shows status "enabled", state "up" for vcenter hosts
Horizon allows to create instances in vcenter availability zone and shows status "building" for them more then an hour (no error)

---------------------------iso version---------------------------------
api: '1.0'
astute_sha: a717657232721a7fafc67ff5e1c696c9dbeb0b95
auth_required: true
build_id: '288'
build_number: '288'
feature_groups:
- mirantis
fuel-agent_sha: 082a47bf014002e515001be05f99040437281a2d
fuel-library_sha: 121016a09b0e889994118aa3ea42fa67eabb8f25
fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
fuel-ostf_sha: 1f08e6e71021179b9881a824d9c999957fcc7045
fuelmain_sha: 6b83d6a6a75bf7bca3177fcf63b2eebbf1ad0a85
nailgun_sha: 93477f9b42c5a5e0506248659f40bebc9ac23943
openstack_version: 2015.1.0-7.0
production: docker
python-fuelclient_sha: 1ce8ecd8beb640f2f62f73435f4e18d1469979ac
release: '7.0'
release_versions:
  2015.1.0-7.0:
    VERSION:
      api: '1.0'
      astute_sha: a717657232721a7fafc67ff5e1c696c9dbeb0b95
      build_id: '288'
      build_number: '288'
      feature_groups:
      - mirantis
      fuel-agent_sha: 082a47bf014002e515001be05f99040437281a2d
      fuel-library_sha: 121016a09b0e889994118aa3ea42fa67eabb8f25
      fuel-nailgun-agent_sha: d7027952870a35db8dc52f185bb1158cdd3d1ebd
      fuel-ostf_sha: 1f08e6e71021179b9881a824d9c999957fcc7045
      fuelmain_sha: 6b83d6a6a75bf7bca3177fcf63b2eebbf1ad0a85
      nailgun_sha: 93477f9b42c5a5e0506248659f40bebc9ac23943
      openstack_version: 2015.1.0-7.0
      production: docker
      python-fuelclient_sha: 1ce8ecd8beb640f2f62f73435f4e18d1469979ac
      release: '7.0'

[Alexander Arzhanov (aarzhanov)]

Actual state for 8.0:

Step for reproduce:
1. Deploy cluster in Dualhypervisor mode
2. Run a instance via horizon in vcenter availability zone
3. Disconnect vCenter and MOS

Expected result:
Horizon shows status "disabled", state "down" for vcenter hosts
Horizon does not allow to create instances in vcenter availability zone

Actual result:
Horizon shows status "enabled", state "up" for vcenter hosts
Horizon allows to create instances in vcenter availability zone.
After 56 minutes show error:

Error: Failed to perform requested operation on instance "vc2", the instance has an error status: Please try again later
[Error: Build of instance 447be318-b4ff-46df-93c9-8f997fa02304 aborted: Could not clean up failed build, not rescheduling].

[Roman Podoliaka (rpodolyaka)]

So this sounds like a feature request to me:

currently nova-compute (technically, any other nova-* service) reports its state only based on its own availability and knows nothing about implementation specific details, like vcenter API in case of vmware compute driver.

I suggest we do this upstream first, hence marking as Wishlist. Unfortunately, it's too late to propose this for Mitaka, but we can give it a try in N releae.

[Roman Podoliaka (rpodolyaka)]

Unfortunately, it's too late to propose a spec for Mitaka, let's give it another try in Newton. Marking as Won't Fix for 9.0