| Summary: | java NPE (appy/create/bulk) - Searchguard plugin | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Ricardo Lourenco <rlourenc> | ||||||||
| Component: | Logging | Assignee: | ewolinet | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Xia Zhao <xiazhao> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | medium | ||||||||||
| Version: | 3.3.0 | CC: | aos-bugs, jcantril, lvlcek, rlourenc, tstclair | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Linux | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2017-01-09 14:20:53 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Attachments: |
|
||||||||||
Created attachment 1220863 [details]
es master node
Created attachment 1220865 [details]
_cat_allocation
In the master ES logs, are there entries regarding the searchguard index being created/updated? We should see a different entry for each ES cluster node. In the past we've seen that not having the ACLs configured yet has been cause for those NPE stack traces to be emitted from Searchguard. I think this is an error from us not handling a failure scenario properly: https://github.com/fabric8io/openshift-elasticsearch-plugin/blob/ES1.5.x/src/main/java/io/fabric8/elasticsearch/plugin/ActionForbiddenActionFilter.java#L57 likely related to the seeding problem mentioned by @eric. Nothing in the logs regarding ACL configuration. The master logs are attached to this BZ: https://bugzilla.redhat.com/attachment.cgi?id=1220863 @Eric, That's fine by me, I didn't see this error thus far. |
Created attachment 1220861 [details] es data node Description of problem: During scale-out testing of logging (205 nodes) the following NPE appeared in the elasticsearch logs