-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Exception occurred in runner inventory.audit: Traceback... #8
Comments
Hi, Thanks for adding the detailed issue report. Can you confirm which version of Salt you are running on the Salt master and client(s)? Just to make sure the state of the database is ok, can you delete all records (if there are any) from the minion table and then try running a force audit on a minion? If this does not work, then it would also be useful if you could share the output of your event queue on the Salt master when a minion runs an audit. This can be done by running on the master:
This should show the arguments and their values being passed from the minion to the reactor and finally to the runner. Cheers, Neil. |
Salt server is
Salt minion is
Database is empty and has never been populated so far.
Stripped logs from Bottom error expanded:
Now the error is different, our line 222 is I removed the int(), and restarted, now it is again:
(this is the same error as the one reported above) Our Logs before changing line 222:
|
Thanks for the info. The event log info is interesting as I don't see any selinux values being passed from the minion to the master. Can you run the follow command against your minion from your master:
This will display all of the grain info for your minion. The inventory.audit module function uses the grain values to find out details about a minion. Can you look through the output produced and see if you have a selinux section, e.g.
Can you confirm if you are using selinux or not? E.g. check the output of In the meantime I'll try and set-up an Ubuntu VM to see if I can repeat the issue you are seeing. |
I've set-up an Ubuntu 18.04 server VM and repeated the error. It would appear that selinux is not part of a default install. I'll update the |
Version 1.3 released to fix this bug. Also fixed a bug for the Python3 version of SaltStack when using this module. Can you test this new release (only |
Thanks for working on this, I don't know if that's useful to know, there is still an exception.
it shows:
This is unrelated with force-auditing (happens without starting the following command)
|
Glad to hear the update fixed the initial issue and thanks for letting me know. I take it from the web page you now see your minion(s) and can view their details ok? I'm not sure why you are seeing adding new host error. Do you have any other minions or just the one? The full output of the event queue from the Salt master would be useful to try and identify how this is being triggered. |
I currently have no access to the setup for two weeks. I only checked database content from command line. |
No problem, have a good Christmas ;-) |
Hi,
We are trying your inventory runner, thanks for that,
we are facing issues.
database is setup and working,
module is functionnal,
We added a log line in
__doQuery
:All what we can see in logs are
SELECT
s (noINSERT
,UPDATE
...)and salt logs show lines like that
Line 208 is an access to
properties[]
, all accesses toproperties[]
give this error,The error originally occurs in this line (we added our logs and debugs).
We are not at this point bearded enough to debug the
properties
argument in theaudit
python function.Can you please provide us some help ?
Also, thanks for setting this repository up !
The text was updated successfully, but these errors were encountered: