- VMware Technology Network
- :
- Cloud & SDDC
- :
- ESXi
- :
- ESXi Discussions
- :
- Renaming of VM reverses
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Renaming of VM reverses
Hi!
I need a fresh set of eyes!
We have a script renaming 2 VM's. At the end one is replacing the other name wise. One time out of 50-100 it fails and the first renaming reverses giving the VM same name with additional (1).
Below are events exported from vCenter.
Anyone seen this?
My first thought is that the first renaming was not entirely done when second started and there was conflicts of names but there are 2 seconds between first task finishes and second is starting.
(Bonus question... The VM's are marked as dirty... What does this mean? If I check logs there are both VM's and hosts marked dirty.)
Events from vCenter. Searched for vm-#id and listed. Old VM is vm-97 and new is vm-405.
-Ok-
Renaming first VM(Renamed vm04-orig from vm04 to vm04-orig in lab):
2015-09-10T11:58:52.838+03:00 [7F92184B6700 info 'commonvpxLro' opID=29b5729b] [VpxLRO] -- BEGIN task-4604 -- vm-97 -- vim.ManagedEntity.rename -- f6d6879e-40f2-b25e-b88f-fcf5037abb93(52182a34-aee0-0094-1b69-ea6c51c3cced)
2015-09-10T11:58:52.849+03:00 [7F92184B6700 info 'vmmoVm' opID=29b5729b] [VmMo::SetComputeCompatibilityDirty] vm vm-97 is marked dirty
2015-09-10T11:58:53.620+03:00 [7F9218CC6700 info 'vpxdoverheadMemory'] [OverheadCache::Invalidate] VM vim.VirtualMachine:vm-97: config changed, invalidating cache...
2015-09-10T11:58:53.810+03:00 [7F92184B6700 info 'commonvpxLro' opID=29b5729b] [VpxLRO] -- FINISH task-4604 -- vm-97 -- vim.ManagedEntity.rename --
-Ok-
Renaming second VM(Renamed vm04 from new-vm4 to vm04 in lab):
2015-09-10T11:58:55.788+03:00 [7F9218F4B700 info 'commonvpxLro' opID=21d44b4b] [VpxLRO] -- BEGIN task-4605 -- vm-405 -- vim.ManagedEntity.rename -- 9d3b4fda-4b36-6a2d-8950-ff2fcc7a889d(524c7506-3197-4f03-3f30-9e83a91300d0)
2015-09-10T11:58:55.798+03:00 [7F9218F4B700 info 'vmmoVm' opID=21d44b4b] [VmMo::SetComputeCompatibilityDirty] vm vm-405 is marked dirty
2015-09-10T11:58:56.596+03:00 [7F921985D700 info 'vpxdoverheadMemory'] [OverheadCache::Invalidate] VM vim.VirtualMachine:vm-405: config changed, invalidating cache...
2015-09-10T11:58:56.722+03:00 [7F9218F4B700 info 'commonvpxLro' opID=21d44b4b] [VpxLRO] -- FINISH task-4605 -- vm-405 -- vim.ManagedEntity.rename --
-Here comes the problem(I think)-
Where does this come from? Ends with proof of name changed back for first namechange [vim.VirtualMachine:vm-97,vm04 (1)].
2015-09-10T11:59:26.244+03:00 [7F9218FCC700 info 'vpxdoverheadMemory' opID=HB-host-38@1033-7b7cc91] [OverheadCache::Invalidate] VM vim.VirtualMachine:vm-97: config changed, invalidating cache...
2015-09-10T11:59:26.321+03:00 [7F9218FCC700 info 'vmmoVm' opID=HB-host-38@1033-7b7cc91] [VmMo::SetComputeCompatibilityDirty] vm vm-97 is marked dirty
2015-09-10T11:59:29.955+03:00 [7F9218B43700 info 'vmmoVm' opID=c769cf4] [VmMo::SetComputeCompatibilityDirty] vm vm-97 is marked dirty
2015-09-10T11:59:29.955+03:00 [7F9218B43700 info 'vmmoVm' opID=c769cf4] [VmMo::SetComputeCompatibilityDirty] vm vm-97 is marked dirty
....continues a bunch of times...
2015-09-10T11:59:37.007+03:00 [7F92185B8700 info 'vmmoVm' opID=35f81135] [VmMo::SetComputeCompatibilityDirty] vm vm-97 is marked dirty
2015-09-10T11:59:37.494+03:00 [7F9219EEA700 info 'DAS' opID=HB-host-38@1045-221f7ede] [FdmManager::HandleVmPowerOff] Setting desired state to unprotected for [vim.VirtualMachine:vm-97,vm04 (1)] per master's request
| Description | Type | DateTime | RelatedTask | VM-ID | Target | User |
| Task: Rename virtual machine | Information | den 10 september 2015 11:58:52 | Rename virtual machine | vm-97 | sprintlab377vm04 | root |
| Renamed sprintlab377vm04-orig from sprintlab377vm04 to sprintlab377vm04-orig in sprintlab377 | Warning | den 10 september 2015 11:58:52 | vm-97 | sprintlab377vm04-orig | root | |
| Reconfigured sprintlab377vm04-orig on slabnode607.netact.nsn-rdnet.net in sprintlab377 | Information | den 10 september 2015 11:58:53 | vm-97 | sprintlab377vm04-orig | root | |
| Task: Rename virtual machine | Information | den 10 september 2015 11:58:55 | Rename virtual machine | vm-405 | N16DBVM | root |
| Renamed sprintlab377vm04 from N16DBVM to sprintlab377vm04 in sprintlab377 | Warning | den 10 september 2015 11:58:55 | vm-405 | sprintlab377vm04 | root | |
| Reconfigured sprintlab377vm04 on slabnode609.netact.nsn-rdnet.net in sprintlab377 | Information | den 10 september 2015 11:58:56 | vm-405 | sprintlab377vm04 | root | |
| Renamed sprintlab377vm04 from sprintlab377vm04 to sprintlab377vm04-orig in sprintlab377 | Warning | den 10 september 2015 11:59:24 | vm-97 | sprintlab377vm04 | User | |
| Renamed sprintlab377vm04-orig from sprintlab377vm04-orig to sprintlab377vm04 in sprintlab377 | Warning | den 10 september 2015 11:59:25 | vm-97 | sprintlab377vm04-orig | User | |
| Renamed sprintlab377vm04 (1) from sprintlab377vm04-orig to sprintlab377vm04 (1) in sprintlab377 | Warning | den 10 september 2015 11:59:26 | vm-97 | sprintlab377vm04 (1) |
Any thoughts and/or inputs are welcome!
/Per