Not sure how this happened, but all our Virtual Center templates are now "orphaned". The only thing I can think of is that our hosts were removed from a cluster and then added back in. All the VM's are fine, but we just lost the templates which are on the same datastores.
In any case, it seems that there is no solution for orphaned objects and that they must be removed from the inventory. I can do this, but then how do I import then back in?
We just hit this issue on Tuesday. Restarting the services did not correct the problem. In fact, it actually orphaned an additional template! We had to do the "remove and re-add" process on each template to correct this.
Same problems here as well. Has anyone had a definitive answer from support?
I noticed VC 2.0.2 has been recently released (build 50618). No mention of this bug in the release notes that I can see: http://www.vmware.com/support/vi3/doc/releasenotes_vc202.html
I will perform the upgrade soon enough however and see if it gets better.
banaszyb - thanks for the detailed instructions, very helpful...
so i just spent a bunch of time looking thru the logs from last week trying find what the vmware tech d00d showed me as to what the culprit was as to what was causing my VCB backups to fail.... but i can's seem to find what i was looking for...
but, on the first two attempts at running a VCB backup i noticed in my Virtual Infrastructure Client that ALL of my vm servers were show as "Disconnected"..., and i think they were greyed out, this cleared up within a few seconds.. but was i was told was that the "server" restarted. some daemon with the esx server restarted, there was no core dump , but the main daemon restarted. it happened twice and then everything was cool.
sorry i don't have the log info for some real info but probably this is what is happening for others because now my templates are orphaned
if i can find the log output i'll post it.
Just upgraded our 32 blade server farm to ESX 3.0.2 and VI 2.0.2 from 3.0.1/2.0.1.
We just started to have issues with orphaned VM Templates after the VI upgrade. A simple re-register of all the orphaned templates seems to fix it.
One clue as to why this is happening, after the VI upgrade the agents on all the ESX servers are updated but in the majority of the installs I am hearing reported (by friends and colleagues) this process fails 90% of the time on the first attempt.
This even after following the instructions of making sure that HA is disabled and that all the ESX servers have the /tmp/vmware-root folder prior to upgrading.
I recommend one additional preparatory step, restart the mgmt-vmware service via "service mgmt-vmware restart".
anyway that's my two cents.
We ran into the same issue and opened a support case with VMware on it. They said that this is a known issue and that engineering is working on it. They said that the bug report was fairly recent (August 16 2007) so they haven't had much time to work on it so far.
They also mentioned an additional side effect that I hadn't noticed. If you restart the VC service to fix this problem, you create a new problem. The little green, yellow, and red dots in the "status" column go blank for all of the virtual machines. I guess the fix for that is to restart the VC agent on the hosts, but that seems to be the cause of the templates going offline in the first place...
Ran into the same problem. I tried the work-around of removing from inventory and adding to inventory but that was a tedious process.
I restarted both the SQL Server service and the Virtual Center Server service on the Virtual Center server and I got all the templates back.
They also mentioned an additional side effect that I
hadn't noticed. If you restart the VC service to fix
this problem, you create a new problem. The little
green, yellow, and red dots in the "status" column go
blank for all of the virtual machines. I guess the
fix for that is to restart the VC agent on the hosts,
but that seems to be the cause of the templates going
offline in the first place...
Same here, from time to time I lose all the status lights on my servers and the only fix is once the ESX hosts have booted is to run:
service mgmt-vmware restart
But that then orphans my templates, so I restart the VC service and I lose all the status lights.......
Just to add.....
ESX 3.0.2 / VI 2.0.2
Noticed templates disconnected... could do nothing with them - right click, all options grey except for Add permission... odd. Could not remove from inventory, and could not re-register. Tried restarting VC service - resolved problem for XP templates, not W3K templates.
And yes - the missing status lights as well.
Disabled HA and DRS
Removed host from cluster
Fixed all problems of templates and status lights. Additionaly, for the other host with no templates, I only needed to disconnect and reconnect to get status lights back (caused by the VC restart).
There are so many ways to solve this problem, i think mine was caused by the Storage VMotion to iSCSI SAN even when this VM still got access to the old ESXi ISO folder and then somehow when i convert to template it worked fine.
But not from template into a VM, the way i solved it is just by renaming .VMX into something else and then the conversion process went fine
now ican switch back from Vm to template and back without no problem.
hope this helps.