)
at n.value (http://172.30.129.161:5601/50668/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:400:193699)
at n.value (http://172.30.129.161:5601/50668/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:400:189176)
at n.value (http://172.30.129.161:5601/50668/bundles/kbn-ui-shared-deps-npm/kbn-ui-shared-deps-npm.dll.js:400:188630)
```
Here is a screenshot of the problematic tab:
---
### Author:  [@nchaulet](https://discuss.elastic.co/u/nchaulet)
#### Post date: [May 10, 2022, 2:31pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/2 "2022-05-10T14:31:09Z")
Hi @codewriterguy
I think your configuration got corrupted somehow, we use two different document (saved objects) to store agent policies and package policy and I think you probably have a package policy referring an agent policy that do not exists anymore.
I created a bug ticket in Kibana so we can have a better experience for that [[Fleet] Do not crash when a package policy refer a non existing agent policy · Issue #131928 · elastic/kibana · GitHub](https://github.com/elastic/kibana/issues/131928)
In the mean time you could probably delete the problematic saved object from the `.kibana` index (be carefull of what you delete in that index) and use those queries to find the problematic package policy
```auto
GET .kibana/_search?q=type:ingest-agent-policies
{
"fields": [],
"_source": false
}
GET .kibana/_search?q=type:ingest-package-policies
{
"fields": [
"ingest-package-policies.policy_id"
],
"_source": false
}
```
Let me know if it work for you
---
### Author:  [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [May 11, 2022, 11:09pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/3 "2022-05-11T23:09:51Z")
Thank you for filing a bug ticket on this! I will take a look with these queries and see what I can do, and report back here
---
### Author:  [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [May 17, 2022, 9:24pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/4 "2022-05-17T21:24:17Z")
It turned out to be OK for me to delete all existing agent policies as we're still standing this cluster up. I deleted all agent policies. Your first query shows no hits:
```auto
{
"hits" : {
"total" : {
"value" : 0,
"relation" : "eq"
},
"max_score" : null,
"hits" : []
}
}
```
I still can't delete the integration package though. "Uninstall Recorded Future" is grayed out in Integrations -\> Recorded Future -\> Settings
The second query shows 1 hit with no policy ID:
```auto
"hits" : {
"total" : {
"value" : 1,
"relation" : "eq"
},
"max_score" : 7.779048,
"hits" : [
{
"_index" : ".kibana_8.1.2_001",
"_id" : "ingest-package-policies:c80f1a4a-7b5b-4f20-971c-8d9c350563a5",
"_score" : 7.779048,
"fields" : {
"ingest-package-policies.policy_id" : [
""
]
}
}
]
}
```
---
### Author:  [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [May 17, 2022, 9:25pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/5 "2022-05-17T21:25:12Z")
I did also restart ES + Kibana services after removing all agent policies
---
### Author:  [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [May 17, 2022, 9:27pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/6 "2022-05-17T21:27:15Z")
This is interesting, Management -\> Fleet shows no agent policies but Management -\> Integrations -\> Recorded Future shows 1 agent policy
---
### Author:  [@nchaulet](https://discuss.elastic.co/u/nchaulet)
#### Post date: [May 24, 2022, 1:26pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/7 "2022-05-24T13:26:07Z")
Hi @codewriterguy it seems that there is an orphaned package policy that will need to be deleted
You could probably do so with the following query
```auto
DELETE .kibana/_doc/ingest-package-policies:c80f1a4a-7b5b-4f20-971c-8d9c350563a5
```
Let me know if it helped
---
### Author:  [@codewriterguy](https://discuss.elastic.co/u/codewriterguy)
#### Post date: [May 25, 2022, 9:52pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/8 "2022-05-25T21:52:01Z")
Thank you @nchaulet ! I was able to delete the non-existent agent policy with this command. Very helpful. For reference for anyone visiting this thread I had to delete it with a user with the following role:
```auto
POST /_security/role/kibana_removal_danger
{
"indices": [
{
"names": [".kibana*"],
"privileges": ["create_doc","create","delete","index","write","all"],
"allow_restricted_indices": true
}
]
}
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [June 22, 2022, 9:52pm UTC](https://discuss.elastic.co/t/recorded-future-integration-package-setup-stack-traces/303559/9 "2022-06-22T21:52:11Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.