Reset state unit tests failures
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-cinderclient |
Fix Released
|
Undecided
|
Gorka Eguileor | ||
Bug Description
Depending on the order in which reset status tests are executed we could get failures, which means that we have either tests that mess the system or tests that depend on other tests.
I have narrowed it down quite a bit. If we run "cinderclient.
stdout: {{{'ShellTest' object has no attribute 'reset_state'}}}
Traceback (most recent call last):
File "/home/
return func(self, *args, **kwargs)
File "/home/
return func(*args, **keywargs)
File "/home/
self.
File "/home/
self.
File "/home/
args.
File "/home/
raise exceptions.
cinderclient.
| Changed in python-cinderclient: | |
| assignee: | nobody → Gorka Eguileor (gorka) |
| tags: | added: tests |

Fix proposed to branch: master /review. openstack. org/485197
Review: https:/