# Issues with Fleet after upgrade to 7.11

**URL:** https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021
**Category:** Kibana
**Tags:** fleet, datastreams
**Created:** [February 11, 2021, 1:14pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021 "2021-02-11T13:14:06Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![nemhods](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@nemhods](https://discuss.elastic.co/u/nemhods)
#### Post date: [February 11, 2021, 1:14pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021/1 "2021-02-11T13:14:06Z")

</div>

After an Upgrade to 7.11, i receive Errors about composable templates that back data streams. Because of this, I can't open the Fleet view. The errors occur for seemingly all data streams. The indices have no aliases configured in the Index Management view. I haven't really messed with any of the default index or data stream settings, especially not the "managed" ones.

Below is a sample error from Fleet:

```auto
[illegal_argument_exception] updating component template [metrics-endpoint.metadata-mappings] results in invalid composable template [metrics-endpoint.metadata] after templates are merged response from /_component_template/metrics-endpoint.metadata-mappings: {"error":{"root_cause":[{"type":"illegal_argument_exception","reason":"updating component template [metrics-endpoint.metadata-mappings] results in invalid composable template [metrics-endpoint.metadata] after templates are merged"}],"type":"illegal_argument_exception","reason":"updating component template [metrics-endpoint.metadata-mappings] results in invalid composable template [metrics-endpoint.metadata] after templates are merged","caused_by":{"type":"illegal_argument_exception","reason":"template [metrics-endpoint.metadata] has alias and data stream definitions"}},"status":400}

```

neither `metrics-endpoint.metadata` nor the component template `metrics-endpoint.metadata-mappings` have any aliases defined. Searching for the term "metadata" in `_cat/aliases` does not turn up any results.

---

<div class="post-metadata">

### Author: ![dosant](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dosant/32/64489_2.png) [@dosant](https://discuss.elastic.co/u/dosant)
#### Post date: [February 11, 2021, 1:28pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021/2 "2021-02-11T13:28:26Z")

</div>

Hi @nemhods,

Sorry for the inconveniences,  
There is an open bug, you can subscribe for the updates:

> <https://github.com/elastic/kibana/issues/90984>
>
> Description
> Upgrade to Fleet from 7.10 to 7.11 failed with that error:

---

<div class="post-metadata">

### Author: ![nemhods](https://avatars.discourse-cdn.com/v4/letter/n/48db29/32.png) [@nemhods](https://discuss.elastic.co/u/nemhods)
#### Post date: [February 11, 2021, 1:34pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021/3 "2021-02-11T13:34:22Z")

</div>

Hey,

thanks for the quick update. I'll see if I can contribute.

---

<div class="post-metadata">

### Author: ![skh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/skh/32/38637_2.png) [@skh](https://discuss.elastic.co/u/skh)
#### Post date: [February 11, 2021, 2:48pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021/4 "2021-02-11T14:48:29Z")

</div>

Hi @nemhods,

we've provided a manual workaround in the linked github issue.

---

<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: [March 11, 2021, 2:49pm UTC](https://discuss.elastic.co/t/issues-with-fleet-after-upgrade-to-7-11/264021/5 "2021-03-11T14:49:21Z")

</div>

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