yahoo-eng-team team mailing list archive

[Marcin Zbik <zbikmarc+launchpad@xxxxxxxxx>]

Public bug reported:

VMware driver does not change compute node state (from :-) to XXX) when
it lost connection to vCenter.

api_retry_count does not affect it at all.

When connection to vCenter is lost and nova-compute is restarted it
works. But it does not without restarting. After restart state is
changed to XXX and nova-compute is still polling API connection (good
behavior) but without restart nova-compute has still smile state despite
of " SessionConnectionException: NV-06475AF urllib2 error in
RetrieveServiceContent: : <urlopen error [Errno 113] EHOSTUNREACH>"

Steps to reproduce:
1. Configure nova-compute to connect to VMware vCenter using vmware community driver.
2. Check state of compute-node, it should be available
3. Disconnect vCenter - for example just disconnect network from it
4. Check state of compute-node, it still be available

Expected result:
compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute.

** Affects: nova
     Importance: Undecided
         Status: New


** Tags: vmware

** Description changed:

  VMware driver does not change compute node state (from :-) to XXX) when
  it lost connection to vCenter.
  
  api_retry_count does not affect it at all.
  
  When connection to vCenter is lost and nova-compute is restarted it
  works. But it does not without restarting. After restart state is
- changeg to XXX and nova-compute is still polling API connection (good
+ changed to XXX and nova-compute is still polling API connection (good
  behavior) but without restart nova-compute has still smile state despite
  of " SessionConnectionException: NV-06475AF urllib2 error in
  RetrieveServiceContent: : <urlopen error [Errno 113] EHOSTUNREACH>"
  
  Steps to reproduce:
  1. Configure nova-compute to connect to VMware vCenter using vmware community driver.
  2. Check state of compute-node, it should be available
  3. Disconnect vCenter - for example just disconnect network from it
  4. Check state of compute-node, it still be available
  
  Expected result:
  compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute.

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1316928

Title:
  VMware driver does not change compute node state to unavailable after
  disconnecting from vCenter

Status in OpenStack Compute (Nova):
  New

Bug description:
  VMware driver does not change compute node state (from :-) to XXX)
  when it lost connection to vCenter.

  api_retry_count does not affect it at all.

  When connection to vCenter is lost and nova-compute is restarted it
  works. But it does not without restarting. After restart state is
  changed to XXX and nova-compute is still polling API connection (good
  behavior) but without restart nova-compute has still smile state
  despite of " SessionConnectionException: NV-06475AF urllib2 error in
  RetrieveServiceContent: : <urlopen error [Errno 113] EHOSTUNREACH>"

  Steps to reproduce:
  1. Configure nova-compute to connect to VMware vCenter using vmware community driver.
  2. Check state of compute-node, it should be available
  3. Disconnect vCenter - for example just disconnect network from it
  4. Check state of compute-node, it still be available

  Expected result:
  compute-node should be unavailable when vCenter is disconnected (maybe after api_retry_count?) without need to restart nova-compute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1316928/+subscriptions