ISMPolicy Question

[mrvdcsg]

I am creating an ism policy to delete all security-auditlog-* indexes after 7 days as cleanup of these logs is not available by default. I see that creation of ism policies is now part of the newest operator version (though not yet part of a release). I deployed the operator via source rather than the v2.4 version so it would include these crd and while I don't get any errors, the ISM Policy doesn't get created.

apiVersion: opensearch.opster.io/v1
kind: OpenSearchISMPolicy
metadata:
  name: auditlog-cleanup
  namespace: opensearch
spec:
  opensearchCluster:
    name: opensearch-cluster-1
  description: A policy that deletes security-auditlog indices after 7 days
  policyId: auditlog-cleanup
  defaultState: normal
  states:
    - name: normal
      actions: []
      transitions:
        - stateName: delete
          conditions:
            minIndexAge: "7d"
    - name: delete
      actions:
        - delete: {}
  ismTemplate:
    indexPatterns:
      - "security-auditlog-*"

To note, my cluster is in the "opensearch" namespace and the cluster name is "opensearch-cluster-1". After this is run, I don't see any difference in the cluster including when I look for ISM Policy definitions.

GET _opendistro/_ism/policies
{
"policies": [],
"total_policies": 0
}

I don't think this is due to timing because it doesn't matter how long I wait and I know this is new functionality as of November 2023 but I have an environment deployed with flux and this is the most seamless way to create this policy on current and future clusters.
Anyone else having this issue? Do you see anything I'm doing wrong? Anything to suggest trying? All help appreciated!

[mrvdcsg]

In case someone else is looking for answers:
This will be fixed with the next release of the operator. In the meantime, Julien created an intermediate release. Note that this is suitable for non-production environments to test functionality not yet released as it is not on the main trunk for the Opensearch Operator.

[mrvdcsg]

Now that Operator 2.5.1 was released, I was able to test creating my ISM policies again and it creates perfectly but appears to have a bug in detecting if a policy already exists. I see an error repeating in events: 0s Warning OpensearchAPIError opensearchismpolicy/auditlog-cleanup failed to get policy from Opensearch API
That error appears to be coming from checking for existingpolicy
existingPolicy, retErr := services.GetPolicy(r.ctx, r.osClient, policyId) if retErr != nil && retErr != services.ErrNotFound { reason = "failed to get policy from Opensearch API" r.logger.Error(retErr, reason) r.recorder.Event(r.instance, "Warning", opensearchAPIError, reason) return }
Anyone have a similar experience or know what I might have done wrong?

[mrvdcsg]

Closing this discussion. I'm not seeing this issue continuing in the lab environment after upgrading to Operator 2.6.1.