Failed to get roles that already exist skipping role import – How to solve this Elasticsearch exception

Opster Team

August-23, Version: 6.8-7.17

Briefly, this error occurs when Elasticsearch is unable to retrieve existing roles during a role import process, possibly due to a connectivity issue or incorrect permissions. To resolve this, ensure that Elasticsearch has the necessary permissions to access the roles. Also, check the network connectivity between Elasticsearch and the source of the roles. If the issue persists, consider reconfiguring your roles or reindexing your data.

This guide will help you check for common problems that cause the log ” failed to get roles that already exist; skipping role import ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.

Log Context

Log “failed to get roles that already exist; skipping role import” class name is We extracted the following from Elasticsearch source code for those seeking an in-depth context :

 Map roles = FileRolesStore.parseRoleDescriptors(rolesFile; logger; true; Settings.EMPTY; null);
 Set existingRoles;
 try {
 existingRoles = getRolesThatExist(terminal; env.settings(); env; options);
 } catch (Exception e) {
 throw new ElasticsearchException("failed to get roles that already exist; skipping role import"; e);
 if (rolesToMigrate.length == 0) {
 rolesToMigrate = roles.keySet().toArray(new String[roles.size()]);
 for (String roleName : rolesToMigrate) {


How helpful was this guide?

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?