PVE tries to lock wrong path on creating VM?

[mumblefish]

Hello all,

I have two stand-alone nodes with PVE 8.3.3 which I built about a week ago.
On Node A I had no problem building a VM with Rocky Linux, all good.

Trying to create another VM fails, and I can see form the console that it timed out locking a storage path that I definitely did not specify.
I found the same issue right now on Node B - which had no VM on it at all yet. All I can think of is that maybe a recent update has jogged a tiny switch somewhere?

On a related note, after a while the VMs that showed a lock failed vanish from the list in the node... does that mean they get removed from the system, and I can not verify the settings they think they had now? Or are they in some "attic" somewhere and can be inspected and re-tried?

Many thanks!
mumblefish

 

[Moayad]

Hi,


Hard to say without checking the syslog during the time of the failure. Could you please post the syslog?

 

[mumblefish]

Hi Moayad,

I
am
mortified
....

...not only should I have thought to look at the logs, but also I was absolutely wrong in my assessment of my build profile.
No blame attaches to Proxmox - Problem entirely in chair, not in computer!

Many thanks for jumping in, and I shall be more careful next time before posting!

Cheers,
mumblefish