topic Re: Handling locked by another session issue in Ansible playbooks in Ansible

Handling locked by another session issue in Ansible playbooks

Govind135438 — Mon, 24 Nov 2025 08:39:28 GMT

I am facing the error like below from Ansible playbook from modules from "check_point.mgmt" collection.

TASK [Add VLAN interface to Management gateway object] ************************************************************************************************************** fatal: [10.25.58.51]: FAILED! => {"changed": false, "msg": "Checkpoint device returned error 400 with message {'code': 'generic_error', 'message': \"Action cannot be executed on object: gw-893628 due to: Object 'gw-893628' is locked by another session.\"} Unpublished changes were discarded"}

This error occurs when I have some unpublished changes from Check Point Smartconsole or command-line.

How can I force changes from Ansible when there are unpublished changes from others? Or what is the best practice to follow in this scenario?

Re: Handling locked by another session issue in Ansible playbooks

Daniel_Kuhl1 — Mon, 24 Nov 2025 10:21:50 GMT

A quick answer from my mind without any validation from documentation:

Run show-sessions API call to get all sessions
Then looping through the sessions and find sessions with locks using show-session API call
- take-over the session
- discard or publish to get rid of the locks
continue with your changes

...but I think the Ansible collection does not support all of it, so you have to build your own API calls using Web-Services API.

Maybe CheckMates folks find a better way.

Re: Handling locked by another session issue in Ansible playbooks

Govind135438 — Mon, 24 Nov 2025 12:01:47 GMT

Thank you for your response. I will try your solution.

Re: Handling locked by another session issue in Ansible playbooks

Duane_Toler — Mon, 24 Nov 2025 14:46:26 GMT

You can't publish another session, reliably, even if your administrator account has access to do so. You don't want to do this. Instead, you need to open SmartConsole -> Manage & Settings -> Sessions and see who has open sessions and object locks. You either need to discard those sessions (if you have permissions to do so), or ask the other administrators to close their sessions. The management server is trying to protect you from unwanted, and unexpected, results that you may not want. Don't violate this or you will have trouble.