# Eck-operator error logs

**URL:** <https://discuss.elastic.co/t/eck-operator-error-logs/312459>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [August 19, 2022, 11:21am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459 "2022-08-19T11:21:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![x00m](https://avatars.discourse-cdn.com/v4/letter/x/90db22/32.png) [@x00m](https://discuss.elastic.co/u/x00m)\
**Post date:** [August 19, 2022, 11:21am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/1 "2022-08-19T11:21:59Z")

</div>

I see a lot of errors coming out of eck operator :

This is one instance:

```auto
E0819 10:51:42.525350 1 leaderelection.go:330] error retrieving resource lock elastic-system/elastic-operator-leader: leases.coordination.k8s.io "elastic-operator-leader" is forbidden: User "system:serviceaccount:elastic-system:elastic-operator" cannot get resource "leases" in API group "coordination.k8s.io" in the namespace "elastic-system"

```

I've also observed the pod keeps restarting.

Using eck 2.3.0

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [August 22, 2022, 6:16am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/2 "2022-08-22T06:16:20Z")

</div>

Since 2.3.0 ECK relies on `coordination.k8s.io/leases` resources for leader election, [see this comment here](https://github.com/elastic/cloud-on-k8s/pull/5662#issuecomment-1127682131). I think you upgraded the operator image without upgrading the [operator role](https://github.com/elastic/cloud-on-k8s/blob/fd19197b64d914e0343622c1c095fc605867c565/deploy/eck-operator/templates/_helpers.tpl#L129-L144).

---

<div class="post-metadata">

**Author:** ![x00m](https://avatars.discourse-cdn.com/v4/letter/x/90db22/32.png) [@x00m](https://discuss.elastic.co/u/x00m)\
**Post date:** [August 22, 2022, 6:49am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/3 "2022-08-22T06:49:31Z")

</div>

This is a fresh installation of ECK 2.3.0 and not an upgrade. Do I have to do anything else to make sure these errors don't show up?

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [August 22, 2022, 7:01am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/4 "2022-08-22T07:01:19Z")

</div>

Interesting, how the ECK operator has been installed?

---

<div class="post-metadata">

**Author:** ![x00m](https://avatars.discourse-cdn.com/v4/letter/x/90db22/32.png) [@x00m](https://discuss.elastic.co/u/x00m)\
**Post date:** [August 23, 2022, 6:00am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/5 "2022-08-23T06:00:34Z")

</div>

Just verified, looks like it is an upgrade. Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [September 20, 2022, 6:01am UTC](https://discuss.elastic.co/t/eck-operator-error-logs/312459/6 "2022-09-20T06:01:24Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.