Kibana version: 7.11.1
Elasticsearch version: 7.11.1
Server OS version: ESS
Browser version: Version 88.0.4324.150 (Official Build) (x86_64)
Browser OS version: macOS Catalina 10.15.7
Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud
Describe the bug:
It showed Policy "cloud-snapshot-policy" is already associated with this repository. when trying to create another SLM policy for found-snapshots repository which policy "cloud-snapshot-policy" is already associated with.
Steps to reproduce:
- Create a deployment on Elastic Cloud (where SLM is enabled by default)
- Create a policy from
Snapshot and Store -> Policies -> Create a policy
- Select default repository
found-snapshots
Expected behavior:
It's working when using Put snapshot lifecycle policy API. It should be able to add another slm policy to repository found-snapshots
https://www.elastic.co/guide/en/elasticsearch/reference/master/slm-api-put-policy.html#slm-api-put-policy
Screenshots (if relevant):

Errors in browser console (if relevant):
N/A
Provide logs and/or server output (if relevant):
N/A
Any additional context:
Kibana version: 7.11.1
Elasticsearch version: 7.11.1
Server OS version: ESS
Browser version: Version 88.0.4324.150 (Official Build) (x86_64)
Browser OS version: macOS Catalina 10.15.7
Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud
Describe the bug:
It showed
Policy "cloud-snapshot-policy" is already associated with this repository.when trying to create another SLM policy for found-snapshots repository which policy "cloud-snapshot-policy" is already associated with.Steps to reproduce:
Snapshot and Store->Policies->Create a policyfound-snapshotsExpected behavior:
It's working when using
Put snapshot lifecycle policy API. It should be able to add another slm policy to repositoryfound-snapshotshttps://www.elastic.co/guide/en/elasticsearch/reference/master/slm-api-put-policy.html#slm-api-put-policy
Screenshots (if relevant):

Errors in browser console (if relevant):
N/A
Provide logs and/or server output (if relevant):
N/A
Any additional context: