api context lock cannot be undone

[alexskysilk]

In the API reference, context set /api2/json/nodes/{node}/lxc/{vmid}/config/lock should be able to reset a container's lock flag, but actually issuing the command errors out with

no 'set' handler for 'nodes/nodeid/lxc/ctid/config/lock'

Does this context work, and what am I doing wrong?

 

[t.lamprecht]

Can you try something like:

pvesh set /nodes/NODEID/lxc/CTID/config -delete lock

A bit non-intuitive at first. config has no lock subpath and secondly you could only use the lock parameter to set a new lock not to clear one completely, that holds true for all config parameters.
Maybe we could add sub paths for properties and allow a delete on them... then "pvesh delete /nodes/NODEID/lxc/CTID/config/lock" could work.

 

[alexskysilk]

issuing the command

pvesh set /nodes/NODEID/lxc/CTID/config -delete lock

results in "CT is locked (snapshot-delete)"

actual lock state isnt removed. Incidentally, this container is locked for a snapshot-delete but no snapshot task is pending, which is how this odyssey started.

 

[t.lamprecht]

Oh, you can always use "pct unlock VMID", just that you know.

I thought you're working on an API client and must use the API for unlocking.

 

[alexskysilk]

You're right, I am working via api. I was using pvesh for convenience. I know it can be done via pct unlock but that would require ssh access.

 

[alexskysilk]

*bump* in case my prior message was not clear, the problem remains, and the api behavior is not as described in the documentation.

 

[dcsapak]

you can add the '-skiplock' parameter to the api call of deleting the lock

 

[alexskysilk]

Unknown option: skiplock
400 unable to parse option

Maybe I'm making the wrong call? can you give me the entire context to call?

 

[dcsapak]

mhmm yeah you are right ( i looked at the qemu api calls and not the container ones)
at the moment for containers it is only possible to unlock it via 'pct unlock VMID'

 

[alexskysilk]

This continues to be a pain in my behind. @dcsapak is there any change this functionality will be added to the api?