Wrong migration step run when file names are the same
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
Fix Released
|
High
|
Ron De Rose |
Bug Description
We've seen a couple instances now where the wrong migration step is run in tests, when the migration file names in each repo are the same. For example, in the following patch, expand was called, yet the contract file was the one actually run:
Traceback (most recent call last):
File "keystone/
self.expand(13)
File "keystone/
self.
File "keystone/
self.
File "/home/
change.
File "/home/
script_
File "/home/
migrate.
File "/home/
raise AttributeError(key)
AttributeError: domain_id
Likewise, morgan was seeing a similar issue here, where the expand migration file wasn't being run, so the test failed the table exist check:
https:/
However, both patches would run successfully locally.
As a workaround, making the repo file names unique fixes the problem, suggesting that perhaps this is related to the files being cached.
description: | updated |
description: | updated |
description: | updated |
Changed in keystone: | |
assignee: | nobody → Ron De Rose (ronald-de-rose) |
tags: | added: sql |
Changed in keystone: | |
importance: | Undecided → High |
Changed in keystone: | |
status: | New → In Progress |
Changed in keystone: | |
milestone: | none → pike-1 |
good catch! that's why we see some strange behavior in the banned operations tests