Commit cb4e8387 authored by Iustin Pop's avatar Iustin Pop
Browse files

Fix instance rename

As can be seen from the patch, we remove from the locking manager However, we do this right after cfg.RenameInstance, which
changes to the new name. So we need to remove old_name not
the new name.

The real question is why does the glm allow me to remove a not-existing
instance name...

The symptom before the patch was: run rename, then:
$ gnt-instance list
Unhandled protocol error while talking to the master daemon:
Caught exception: 'NoneType' object has no attribute 'primary_node'

Reviewed-by: imsnah
parent 01f3e7b1
......@@ -2558,7 +2558,7 @@ class LURenameInstance(LogicalUnit):
self.cfg.RenameInstance(, self.op.new_name)
# Change the instance lock. This is definitely safe while we hold the BGL
self.context.glm.remove(locking.LEVEL_INSTANCE, old_name)
self.context.glm.add(locking.LEVEL_INSTANCE, self.op.new_name)
# re-read the instance from the configuration after rename
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment