UUID field setting in InstanceMapping
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
see this warning in unit test
/home/
"for further details" % value, FutureWarning)
the problem is bigger than a warning when the code change, as we have some code here in nova/cmd/manage.py , this will make the instance uuid not acceptable in the real code
1365 # Don't judge me. There's already an InstanceMapping with this UUID
1366 # so the marker needs to be non destructively modified.
1367 next_marker = next_marker.
1368 objects.
1369 project_
1370 return 1
Changed in nova: | |
assignee: | nobody → jichenjc (jichenjc) |
Changed in nova: | |
assignee: | jichenjc (jichenjc) → nobody |
We have these all over the unit tests in nova, there is some other bug for them I think that people were working in newton, so not sure we need a bug for this, it could just be fixed, but this is fine.