container locked after unsuccessful snapshot removal

[michabbs]

I had this:

TASK ERROR: zfs error: cannot destroy snapshot rpool/data/subvol-101-disk-0@pb1589489673: dataset is busy

Actually nothing special - dataset was indeed busy, so snapshot couldn't be removed. But the container stayed in the "locked" state, so it was impossible to remove it later:

TASK ERROR: CT is locked (snapshot-delete)

I manually did pct unlock and everything works fine, but... did Proxmox behave correctly? I see no reason why the container stayed locked.

 

[wolfgang]

I manually did pct unlock and everything works fine, but... did Proxmox behave correctly?

Yes.
Locks stay to inform the admin that something went wrong.

I see no reason why the container stayed locked.

To remove the snapshot what failed to remove.