← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1300810] Re: test_availability_zone_detail v3 API sample test is racey

 

** Also affects: nova/icehouse
   Importance: Undecided
       Status: New

** Changed in: nova/icehouse
       Status: New => Fix Committed

** Changed in: nova/icehouse
    Milestone: None => 2014.1.1

-- 
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/1300810

Title:
  test_availability_zone_detail v3 API sample test is racey

Status in OpenStack Compute (Nova):
  Fix Committed
Status in OpenStack Compute (nova) icehouse series:
  Fix Committed

Bug description:
  The failure occurs when tests are run on a slower machine.  Or it can
  be reproduced by introducing a time.sleep(5) at the start of the
  nova/tests/integrated/v3/test_availability_zone.py:test_availability_zone_detail
  method.

  11:48:26 raise NoMatch('\n'.join(error))
  11:48:26 NoMatch: Extra list items in template:
  11:48:26 {u'zone_name': u'internal', u'hosts': {u'network': {u'nova-network': {u'active': True, u'available': True, u'updated_at': None}}, u'conductor': {u'nova-conductor': {u'active': True, u'available': True, u'updated_at': None}}, u'cells': {u'nova-cells': {u'active': True, u'available': True, u'updated_at': None}}, u'cert': {u'nova-cert': {u'active': True, u'available': True, u'updated_at': None}}, u'scheduler': {u'nova-scheduler': {u'active': True, u'available': True, u'updated_at': None}}, u'consoleauth': {u'nova-consoleauth': {u'active': True, u'available': True, u'updated_at': None}}}, u'zone_state': {u'available': True}}
  11:48:26 {u'zone_name': u'nova', u'hosts': {u'compute': {u'nova-compute': {u'active': True, u'available': True, u'updated_at': None}}}, u'zone_state': {u'available': True}}
  11:48:26 Extra list items in Response:
  11:48:26 {u'zone_name': u'internal', u'hosts': {u'network': {u'nova-network': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:14.130232'}}, u'conductor': {u'nova-conductor': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:13.843489'}}, u'cells': {u'nova-cells': {u'active': True, u'available': True, u'updated_at': None}}, u'cert': {u'nova-cert': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:13.868539'}}, u'scheduler': {u'nova-scheduler': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:14.397896'}}, u'consoleauth': {u'nova-consoleauth': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:13.872836'}}}, u'zone_state': {u'available': True}}
  11:48:26 {u'zone_name': u'nova', u'hosts': {u'compute': {u'nova-compute': {u'active': True, u'available': True, u'updated_at': u'2014-03-31T16:01:13.863846'}}}, u'zone_state': {u'available': True}}

  Once the services are started they will eventually update their
  updated_at time, but it doesn't happen immediately.  So the sample
  check fails because it's expecting updated_at to be None but it could
  have a timestamp value.

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


References