Uploaded image for project: 'Data Foundation Bugs'
  1. Data Foundation Bugs
  2. DFBUGS-2722

Bucket life cycle policy is not able to process object tags if ILM is enabled

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Undefined Undefined
    • odf-4.20
    • odf-4.18.4
    • noobaa-nc
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Committed
    • ?
    • ?
    • Committed
    • Release Note Not Required
    • Critical
    • Proposed
    • None

       

      Description of problem - 
      BLC is not able to process the policy with object tags if ILM is enabled.
      If the policy is ran via POSIX (NC_LIFECYCLE_GPFS_ILM_ENABLED = true) , it is able to process the tags

       

      The OCP platform infrastructure and deployment type (AWS, Bare Metal, VMware, etc. Please clarify if it is platform agnostic deployment), (IPI/UPI):
      Scale

       

      The version of all relevant components (OCP, ODF, RHCS, ACM whichever is applicable):
      noobaa-core-5.18.4-20250527.el9.x86_64
      Scale : 5.2.3.1

       

       

      Does this issue impact your ability to continue to work with the product?

      No, I can continue with other BLC policies with out tags

       

      Is there any workaround available to the best of your knowledge?

      No

       

      Can this issue be reproduced? If so, please provide the hit rate

      Yes . Can be reproduced

       

      Steps to Reproduce:

      1. In the cluster make sure that ILM is enabled

      [root@bright-31 ~]# jq . /mnt/cesSharedRoot/ces/s3-config/config.json | grep ILM
        "NC_LIFECYCLE_GPFS_ILM_ENABLED": true

      2. create a bucket and upload some objects with tags

      [root@fa-akarattu-mgmt-host rules]# account7000 s3api put-object --bucket bucket7000 --key file101.txt --body file100.txt --tagging "tag1=value1"

      {     "ETag": "\"mtime-daeqvhjxov0g-ino-k3f\"" }

      [root@fa-akarattu-mgmt-host rules]# account7000 s3api get-object-tagging --bucket bucket7000 --key file100.txt
      {
          "TagSet": [
             

      {             "Key": "tag1",             "Value": "value1"         }

          ]
      }

      3. Upload below bucket policy with tags
      {
          "Rules": [
              {
                  "Expiration":

      {                 "Days": 1             }

      ,
                  "ID": "Exp-adv",
                  "Filter": {
                      "And": {
                          "Prefix": "file",
                          "Tags": [
                             

      {                             "Key": "tag1",                             "Value": "value1"                         }

                          ],
                          "ObjectSizeGreaterThan": 10240,
                          "ObjectSizeLessThan": 204800
                      }
                  },
                  "Status": "Enabled"
              }
          ]
      }

      4. Now run the policy and watch the result. --> Inside the run report, I can see the below error

        "total_stats":

      {     "num_objects_deleted": 0,     "num_objects_delete_failed": 0,     "objects_delete_errors": [],     "num_mpu_aborted": 0,     "num_mpu_abort_failed": 0,     "mpu_abort_errors": []   }

      ,
        "state":

      {     "is_finished": false   }

      ,
        "buckets_statuses": {},
        "errors": [
          "create_candidates_file_by_gpfs_ilm_policy failed with error Error: Command failed: mmapplypolicy /mnt/gpfs0 -P /var/log/noobaa/lifecycle/lifecycle_ilm_policies/noobaa_ilm_policy_%2Fmnt%2Fgpfs0_1749141542859 -f /var/log/noobaa/lifecycle/lifecycle_ilm_candidates -I defer\n[E:-1] Error while loading policy rules.\nPCSQLERR: 'VALUE1' is an unsupported or unknown attribute or variable name in this context.\nPCSQLCTX: at line 12 of 26: AND XATTR('user.noobaa.tag.tag1') LIKE {value1}\n[E] Summary of errors:: _serious unclassified errors:1.\nmmapplypolicy: Command failed. Examine previous error messages to determine cause.\n",
          "create_candidates_file_by_gpfs_ilm_policy failed with error Error: Command failed: mmapplypolicy /mnt/gpfs0 -P /var/log/noobaa/lifecycle/lifecycle_ilm_policies/noobaa_ilm_policy_%2Fmnt%2Fgpfs0_1749141542859 -f /var/log/noobaa/lifecycle/lifecycle_ilm_candidates -I defer\n[E:-1] Error while loading policy rules.\nPCSQLERR: 'VALUE1' is an unsupported or unknown attribute or variable name in this context.\nPCSQLCTX: at line 12 of 26: AND XATTR('user.noobaa.tag.tag1') LIKE {value1}\n[E] Summary of errors:: _serious unclassified errors:1.\nmmapplypolicy: Command failed. Examine previous error messages to determine cause.\n",
          "create_candidates_file_by_gpfs_ilm_policy failed with error Error: Command failed: mmapplypolicy /mnt/gpfs0 -P /var/log/noobaa/lifecycle/lifecycle_ilm_policies/noobaa_ilm_policy_%2Fmnt%2Fgpfs0_1749141542859 -f /var/log/noobaa/lifecycle/lifecycle_ilm_candidates -I defer\n[E:-1] Error while loading policy rules.\nPCSQLERR: 'VALUE1' is an unsupported or unknown attribute or variable name in this context.\nPCSQLCTX: at line 12 of 26: AND XATTR('user.noobaa.tag.tag1') LIKE {value1}\n[E] Summary of errors:: _serious unclassified errors:1.\nmmapplypolicy: Command failed. Examine previous error messages to determine cause.\n"
        ]

      Note : Tags are processed successfully with out ILM

      The exact date and time when the issue was observed, including timezone details:

       

      Expected results:
      Since POSIX is able to proceed , user would expect ILM will also be able to process object tags.

       

      Logs collected and log location:

       

       

       
       

              rayalon@redhat.com Rom Ayalon (Inactive)
              anandhu198410 Anandhu Karattuparambil
              Rom Ayalon (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: