I wrote a Tempest test for making sure that resizing a stopped server works since the API supports that scenario, and Jenkins passes (with the libvirt driver) but XenServer CI failed on the new tests:
http://dd6b71949550285df7dc-dda4e480e005aaa13ec303551d2d8155.r49.cf1.rackcdn.com/12/87312/3/testr_results.html.gz
Traceback (most recent call last):
File "tempest/api/compute/servers/test_server_actions.py", line 220, in test_resize_server_confirm_from_stopped
self._test_resize_server_confirm(stop=True)
File "tempest/api/compute/servers/test_server_actions.py", line 201, in _test_resize_server_confirm
self.client.wait_for_server_status(self.server_id, 'VERIFY_RESIZE')
File "tempest/services/compute/json/servers_client.py", line 168, in wait_for_server_status
raise_on_error=raise_on_error)
File "tempest/common/waiters.py", line 89, in wait_for_server_status
raise exceptions.TimeoutException(message)
TimeoutException: Request timed out
Details: Server a3bdc31f-c8db-4751-af96-db9e17ce744c failed to reach VERIFY_RESIZE status and task state "None" within the required time (196 s). Current status: ACTIVE. Current task state: None.
Hmm, looks like this could be an environment issue with the XenServer CI.
Either way, looks like it should be investigated a little more form the XenServer CI point of view.