Migrate button grayed out on a VM in Vsphere Web client.

In vCenter Server, what would cause the Migrate link to be grayed out on a VM?  T

Task in Progress,

Edit Settings also grayed out ?

Huh.  In the intervening hour(?) or so since I posted this, the migrate button is now normal.  I had checked and there were no active tasks.  I give up.  There is still a .lck file in that VM's folder though that has a datestamp on it over a month ago:

-rw-r--r--    1 root     root          1442 Feb 12 02:41 SMTest-3e3f864e.hlog
-rw-------    1 root     root            13 Feb 12 02:41 SMTest-aux.xml
-rw-------    1 root     root     4294967296 Jun 23 11:44 SMTest-d169f214.vswp
-rw-------    1 root     root          8684 Jul 17 13:09 SMTest.nvram
-rw-------    1 root     root            46 Jul 25 17:49 SMTest.vmsd
-rwxr-xr-x    1 root     root          8644 Jul 25 17:49 SMTest.vmx
-rw-------    1 root     root             0 Jun 23 11:44 SMTest.vmx.lck
-rw-------    1 root     root          3382 Jul 10 08:31 SMTest.vmxf
-rwxr-xr-x    1 root     root          8651 Jul 25 17:49 SMTest.vmx~
-rw-------    1 root     root       4915712 Jul 25 15:21 SMTest_10-ctk.vmdk
-rw-------    1 root     root     161061273600 Jul 25 19:09 SMTest_10-flat.vmdk
-rw-------    1 root     root           615 Jul 25 15:20 SMTest_10.vmdk
-rw-------    1 root     root       4915712 Jul 25 17:50 SMTest_12-ctk.vmdk
-rw-------    1 root     root     161061273600 Jul 25 19:09 SMTest_12-flat.vmdk
-rw-------    1 root     root           615 Jul 25 17:49 SMTest_12.vmdk
-rw-------    1 root     root        223362 Feb 12 02:41 vmware-3.log
-rw-------    1 root     root        284175 Feb 12 02:41 vmware-4.log
-rw-------    1 root     root       1261934 Feb 12 02:41 vmware-5.log
-rw-r--r--    1 root     root      15526749 Mar  8 07:28 vmware-6.log
-rw-r--r--    1 root     root      58881562 Jun 15 09:31 vmware-7.log
-rw-r--r--    1 root     root       5082714 Jun 23 11:30 vmware-8.log
-rw-r--r--    1 root     root      18070133 Jul 25 19:07 vmware.log
-rw-------    1 root     root      88080384 Jun 23 11:44 vmx-SMTest-3513381396-1.vswp

Could that cause heartburn to vSphere?

--Ben

Snapshot merge operation possibly.... (you'll not see active tasks, as they could be background process in ESXi)

I would not pay much attention to lock files!

Not sure what do do with a question whose problem heals itself.  I hate those kind--problems that go away by themselves, come back by themselves.

you need to investigate the processes at the time of the issue and what was happening before the event and also the reason for why you also wanted to Migrate and if before the event what steps you had put in motion. But it’s now moot.

I hadn't needed to migrate until a Veam replication took 2+ hours due to vSphere taking that long to delete a 1 gig snapshot.  That suggested to me there might be an underlying hardware issue with the disk this VM is on, so I was considering migrating that VM to another drive.

There isn't much in the way of 'chkdsk' in the vSphere world...

suggests to me the task was still active!

snapshot removal can sometimes take hours sometimes seconds depends on many factors speed of disk I/o in VM datastore iops at the time.

again SSH and ESXi bash shell is your friend

do not rely ever on what you do not see in the GUI

LOL.  Thank you.  I did ssh into the folder (which is how I got the listing I posted).  Are there other commands I can use to determine active tasks?  The Veeam replication job finished.  BTW, another replication finished too in the intervening time from initial posting, so apparently this was an anomaly of some type.

Difficult to fault find now it's over.