-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check_point.gaia.cp_gaia_user_facts error 500 General Exception #62
Comments
Check your /var/log/gaia_api_server.log for internal details on this. The real error is in this log file. It's probably the same bug with Gaia API 1.7 and lower. Likewise, make sure you have a recent Jumbo HFA which includes internal Gaia CONFD (Clish) fixes for running commands via Ansible. There was an issue dealing with the internal CONFD database lock between sessions via the Ansible Gaia modules. Similarly, there is an issue in older versions with inconsistency applying changes for both static routes and dynamic routing processes. Your Gaia API module collection is also outdated. You should update that as well: https://galaxy.ansible.com/ui/repo/published/check_point/gaia |
|
The error above is from a
Whats weird is:
|
Yeah that's interesting. It died on running the CLISH command "show user lock-out" for the list of users. This command is being ran so that Gaia API can return a bunch of useful information for each of the users since you did "cp_gaia_user_facts" to get a list of all the users. (you probably knew this already) You can run these commands manually yourself to "follow the trail", and you might be able to find the missing piece. Login to the gateway, go to CLISH, then run "show users". For each of your users, run "show user lock-out". I looked over the R81.10 JHF notes and didn't see anything interesting in Take 173 that might've already been fixed, either. |
As a workaround:
specifying the lower version (1.7 in this case) worked. So there must be something fishy in the 1.8 version. |
Indeed, or at least v1.8 on R81.10. You still might want to check /config/active and still run the CLISH commands manually to see if you can find it before you open a TAC case. Another point to consider: I saw your Ansible playbook is using the username "ansible_user" (perfectly fine), but does this "ansible_user" have read-write and adminRole permissions? I wonder if there's something odd in the RBA configuration when this user runs these commands, versus "admin" (for example). Either way, you have found some sort of issue, and it warrants additional review by TAC, since it works on API v1.7 and not v1.8. |
@duanetoler yes, that user has the adminRole (I just redacted the name) |
Ok, good, just wanted to be sure; TAC will ask you about that. :) You're welcome to do a TAC case, as R81.10 still supported. However, be aware that R81.10 is going EoL in July 2025 so you'll be better served updating to R81.20 if you can. |
We are using this collection to query the users on gaia gateways
fails with following error:
Other tasks are working fine.
Is this related to: #60 ?
Versions used:
The text was updated successfully, but these errors were encountered: