# Why I am getting this manage\_inference error when using the elasticsearch python library?

**URL:** <https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289>\
**Category:** Logstash\
**Created:** [November 10, 2024, 5:55pm UTC](https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289 "2024-11-10T17:55:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![977db4bf8694e7df28b0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/977db4bf8694e7df28b0/32/50920_2.png) [@977db4bf8694e7df28b0](https://discuss.elastic.co/u/977db4bf8694e7df28b0)\
**Post date:** [November 10, 2024, 5:55pm UTC](https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289/1 "2024-11-10T17:55:21Z")

</div>

I am using elasticsearch python library with api access to the cluster. The api has manage previliges for the indices I am processing but seems to fail for 8.15.1 cluster but works fine for all the others. I tried it with elasticsearch8 too and seem to be the same issue.

 ![1000067009](https://us1.discourse-cdn.com/elastic/original/3X/7/8/7808dd4623af1e32b3f7c6a2905ba23794cedd40.jpeg)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 10, 2024, 6:56pm UTC](https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289/2 "2024-11-10T18:56:37Z")

</div>

Hi @977db4bf8694e7df28b0 Welcome to the community.

First, please do not post images of text, they are hard to read, some can not see them at all, and they can not be searched, debuged, etc.

Many people will not even help with they see pictures of text

 ![Screenshot 2024-11-10 at 10.41.06 AM](https://us1.discourse-cdn.com/elastic/original/3X/a/4/a4734f9d62aa91a2eecdb2d8a2278da93ca5b74e.png)

It looks to me like you are using version 7 of the library, which will probably not support that setting, as it does not exist in version 7 of Elasticsearch

> [@977db4bf8694e7df28b0](#):
>
> The api has manage previliges for the indices I am processing but seems to fail for 8.15.1 cluster but works fine for all the others.

It is not clear exactly what you mean, and definitely use the correct version on the elasticsearch python library to interact with Elasticsearch 8.15.

please Try version 8, show the code, and show the resulting error. (in text)

You will need to show your python code as well... (in text)

What method is occurring on, what are you trying (in text)

Explain what authentication method, user, API key etc., are there security settings etc..etc..etc..

---

<div class="post-metadata">

**Author:** ![977db4bf8694e7df28b0](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/977db4bf8694e7df28b0/32/50920_2.png) [@977db4bf8694e7df28b0](https://discuss.elastic.co/u/977db4bf8694e7df28b0)\
**Post date:** [November 10, 2024, 7:12pm UTC](https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289/3 "2024-11-10T19:12:15Z")

</div>

Hi Stephen, thanks for the reply. As I initially confirmed that I did try 8 too but shows the same error. I am simply using the ccr.follow function which works successfully for other versions of elasticsearch except for the 8.15.1 cluster so may be missing backward compatibility with the error.

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [November 10, 2024, 7:44pm UTC](https://discuss.elastic.co/t/why-i-am-getting-this-manage-inference-error-when-using-the-elasticsearch-python-library/370289/4 "2024-11-10T19:44:20Z")

</div>

Are the two clusters your are CCR the same or different versions?

> [@977db4bf8694e7df28b0](#):
>
> other versions

What other versions.

> [@977db4bf8694e7df28b0](#):
>
> except for the 8.15.1 cluster so may be missing backward compatibility with the error.

That is possible.

You can open an issue but you will need to provide the code. And complete details.

What you have provided is not enough to diagnose.

You could try upgrade to 8.15.3