The Hyper-V CI system is failing all rescue/unrescue tests with errors
similar to this one:
(tempest.api.compute.servers.test_server_rescue_negative.ServerRescueNegativeTestJSON)_StringException:
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
cls.resource_setup()
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
server_id=server_id)
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:
https://review.openstack.org/#/c/127159/
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
functionality...
Thanks,
-jay
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
