test_image_metadata makes assumptions about images
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
Medium
|
David Kranz |
Bug Description
This test fails for me as follows. The test seems to assume that images start with no metadata. My image was a uec image which I guess has some metadata already because the test fails:
Traceback (most recent call last):
File "/root/
self.
AssertionError: {'key2': 'value2'} != {u'owner': None, u'key2': u'value2', u'min_ram': u'0', u'min_disk': u'0'}
- {'key2': 'value2'}
+ {u'key2': u'value2', u'min_disk': u'0', u'min_ram': u'0', u'owner': None}
The test should have a start point of existing metadata, or check for the presence or absence of items after actions rather than comparing for equality.
Changed in tempest: | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: side-effects |
Changed in tempest: | |
assignee: | nobody → Jay Pipes (jaypipes) |
milestone: | none → essex-4 |
Changed in tempest: | |
status: | Triaged → In Progress |
assignee: | Jay Pipes (jaypipes) → David Kranz (david-kranz) |
Changed in tempest: | |
milestone: | none → havana-3 |
This test failure was due to a diablo bug that was fixed in essex and worked around in templest diablo/stable.