Searching for failed to reach ACTIVE status and task state "None"
shows a lot of different bug tickets. This does not seem like a tempest bug. ** Changed in: tempest Status: New => Invalid -- 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/1276778 Title: test_lock_unlock_server: failed to reach ACTIVE status and task state "None" within the required time Status in OpenStack Compute (Nova): New Status in Tempest: Invalid Bug description: Traceback (most recent call last): File "tempest/api/compute/servers/test_server_actions.py", line 419, in test_lock_unlock_server self.servers_client.wait_for_server_status(self.server_id, 'ACTIVE') File "tempest/services/compute/xml/servers_client.py", line 371, 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 c73d5bba-4f88-4279-8de6-9c66844e72e2 failed to reach ACTIVE status and task state "None" within the required time (196 s). Current status: SHUTOFF. Current task state: None. Source: http://logs.openstack.org/47/70647/3/gate/gate-tempest-dsvm- full/b8607e6/console.html To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1276778/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp