tempest

test_get_console_output fails with "Console output was empty"

Bug #1251516 reported by ChangBo Guo(gcb)
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
tempest
New
Undecided
Unassigned

Bug Description

Tempest failed with following backtrace:

Traceback (most recent call last):
  File "tempest/api/compute/servers/test_server_actions.py", line 281, in test_get_console_output
    self.wait_for(get_output)
  File "tempest/api/compute/base.py", line 133, in wait_for
    condition()
  File "tempest/api/compute/servers/test_server_actions.py", line 278, in get_output
    self.assertTrue(output, "Console output was empty.")
  File "/usr/lib/python2.7/unittest/case.py", line 420, in assertTrue
    raise self.failureException(msg)
AssertionError: Console output was empty.

http://logs.openstack.org/07/56507/3/check/check-tempest-devstack-vm-full/4f80690/testr_results.html.gz

Guangya Liu (Jay Lau) (jay-lau-513)
summary: - tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_get_console_output[gate]
+ tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_get_console_output
failed
Revision history for this message
Matt Riedemann (mriedem) wrote :

This is not a duplicate of the MismatchError.

summary: - tempest.api.compute.servers.test_server_actions.ServerActionsTestJSON.test_get_console_output
- failed
+ test_get_console_output fails with "Console output was empty"
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.