Open merlinz01 opened 4 months ago
Added these lines to audit.yml, ran securityadmin.sh, and the errors stopped:
config:
enabled: false
Will be glad when some of this security stuff is streamlined.
The error is when the audit config does not exist (is null). The audit config is being posted to an event bus, which checks the class of the object being posted, and fails when that object is null.
[Triage] Hi @merlinz01, thanks for opening this issue. It looks like you also opened a PR and that was merged. Going to mark as triaged. Thanks again.
What is the bug? I ran securityadmin.sh with an empty audit.yml file and now I'm getting null-pointer exceptions.
How can one reproduce the bug? Retrieve currrent security config with securityadmin.sh. Rename all .yml filenames with dates to their normal names. Edit an unrelated setting in config.yml. Run securityadmin.sh to update the config. Observe this output from securityadmin.sh:
Edit audit.yml and observe that it is empty. Add these lines:
Run securityadmin.sh again and observe this output:
Remove audit.yml and run securityadmin.sh again and observe the same output. See lots and lots of these in Opensearch logs:
What is the expected behavior? No errors
What is your host/environment?
Do you have any screenshots? If applicable, add screenshots to help explain your problem.
Do you have any additional context? Add any other context about the problem.