test_get_console_output_negative fails with: AssertionError: Expected client error, got 200:{"output": ""}
Bug #1392860 reported by
Matt Riedemann
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
http://
Looks like this just cropped up:
23 hits in 24 hours, it's on multiple branches so I'm assuming it's a regression in Tempest.
Looking at recent commits I thought it might be this:
https:/
But I'm not sure.
summary: |
- AssertionError: Expected client error, got 200:{"output": ""} + test_get_console_output_negative fails with: AssertionError: Expected + client error, got 200:{"output": ""} |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/134976 /git.openstack. org/cgit/ openstack/ tempest/ commit/ ?id=12126c20936 f8af169fde09dc4 ed65b7dd473533
Committed: https:/
Submitter: Jenkins
Branch: master
commit 12126c20936f8af 169fde09dc4ed65 b7dd473533
Author: Sean Dague <email address hidden>
Date: Mon Nov 17 10:46:15 2014 -0500
Delete console negative tests
These autogenerated tests are wrong in at least 2 ways, one is
assumptions about when servers are available, and the other a schema
which makes assumptions about the resource end points that are
provably wrong when you look at the Nova code (which is unchanged for
2 years).
It's not clear there is any value generated from these tests, suggest
to delete them.
Related-Bug: #1392860
Change-Id: I4822546f73055e 307017960bd4703 33c81cdea01