[openstack-dev] [nova] Microsoft Hyper-V CI failing all jobs due to rescue functionality

Jay Pipes jaypipes at gmail.com
Sun May 22 23:25:13 UTC 2016

The Hyper-V CI system is failing all rescue/unrescue tests with errors 
similar to this one:

Traceback (most recent call last):
   File "tempest/test.py", line 279, in setUpClass
     six.reraise(etype, value, trace)
   File "tempest/test.py", line 272, in setUpClass
   File "tempest/api/compute/servers/test_server_rescue_negative.py", 
line 59, in resource_setup
     cls.rescue_id, 'RESCUE')
   File "tempest/common/waiters.py", line 75, in wait_for_server_status
tempest.exceptions.BuildErrorException: Server 
2ba65310-80d5-497b-8253-c8aac00fb10e failed to build and is in ERROR status
Details: {u'message': u"Instance 2ba65310-80d5-497b-8253-c8aac00fb10e 
cannot be rescued: Driver Error: 'MaxInternalSize'", u'code': 400, 
u'created': u'2016-05-22T21:59:49Z'}

The above failures are actually *expected* until the following patch lands:


which adds rescue support to the Hyper-V virt driver. Note that the 
Hyper-V CI tests in the above patch are passing properly.

Can we get another nova-core to take a final look at the above patch and 
approve it? That would get the Hyper-V CI tests passing for all open 
Nova patches.

Longer-term, it would probably be good to get some documentation on how 
to appropriately handle the Tempest two-step that needs to occur to 
ensure that functional tests for a particular platform that isn't tested 
in the gate can be run against code that enables that piece of 


More information about the OpenStack-dev mailing list