The random space in rand_name is too small
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tempest |
Fix Released
|
High
|
Unassigned |
Bug Description
Looks like when you using hundreds of name just in 1000000 element space the name collusion can happen and generates false negative results.
It is also can be related with improper teardown.
Several solution is possible:
* Record all generated names, and run the function again if one reoccurs.
- Drawback needs: more memory.
- Can collide with names from improper teardown from previous tempest execution
* Increase the random space.
- Does not grantee uniqueness, but mitigate the collision chance
- UUID make the names much longer
* Incremental name:
- Not really use random, just increment a global number in every request
- Can collide with residues from previous execution
* Combination incremental and random solution together
- the unique like part are constructed from a random number generated once in every execution + an incrementing global number
Additional improvement:
The rand_name should use dashes between the name and unique like part without an explicit request.
Changed in tempest: | |
assignee: | nobody → Attila Fazekas (afazekas) |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in tempest: | |
assignee: | Attila Fazekas (afazekas) → nobody |
Changed in tempest: | |
status: | Triaged → Fix Released |
Changed in tempest: | |
milestone: | none → havana-3 |
Two recent failures resulting from this bug:
http:// logs.openstack. org/20512/ 2/gate/ gate-tempest- devstack- vm-full/ 490/console. html.gz logs.openstack. org/22962/ 2/gate/ gate-tempest- devstack- vm-full/ 6744/console. html.gz
http://