Undefined
Description of problem -
**
Scenario -->In cluster, if multiple filesets are present with buckets created with those fileset path and one of the fileset is unavailable
ILM_ENABLED = true --> No error for the bucket where fileset unlink is done. Runs are proceeding for all buckets.
ILM_ENABLE = false --> Error "No such file or directory" for the bucket where fileset unlink is done. Healthy buckets run continues.
Does this issue impact your ability to continue to work with the product? No
Is there any workaround available to the best of your knowledge? Resolve fileset issue.
Can this issue be reproduced? If so, please provide the hit rate - Yes. Reproducible.
Can this issue be reproduced from the UI? No
If this is a regression, please provide more details to justify this: Not sure
Steps to Reproduce:
- Fileset Creation
Check available filesystem - df -h
Check fileset in the filesystem - mmlsfileset gpfs0 -L , mmlsfileset gpfs0
Create new fileset - mmcrfileset gpfs0 fset1 --inode-space new
Link the fileset - mmlinkfileset gpfs0 fset1 -J /mnt/gpfs0/fset1-dir/
Check fileset in the filesystem - mmlsfileset gpfs0 -L , mmlsfileset gpfs0
Set permission to the fileset path - chmod 775 /mnt/gpfs0/fset1-dir/
- Create account, bucket using fileset path
- Set bucket lifecycle policy on the bucket
- Upload some objects to the bucket
- Unlink the fileset - mmunlinkfileset gpfs0 fset1
Once unlink is done, respective path is unavailable - Set NC_LIFECYCLE_GPFS_ILM_ENABLED to true
- Run the lifecycle policy
The exact date and time when the issue was observed, including timezone details:
Actual results:
**
[root@bl5june-21 ~]# jq . /var/log/noobaa/lifecycle/lifecycle_run_1750087562613.json
{
"running_host": "bl5june-21",
"lifecycle_run_times":
{ .. },
"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": true },
"buckets_statuses": {
..
..
"fset-bucket6": {
"bucket_process_times":
{ "process_bucket_start_time": 1750087567927, "process_bucket_end_time": 1750087567942, "process_bucket_took_ms": 15 },
"bucket_stats": {},
"state":
{ "num_processed_objects": 0, "is_finished": true },
"rules_statuses": {
"Expire-file-objects-on-date": {
"state": {
"expire":
{ "is_finished": true },
"noncurrent": {},
"is_finished": true
},
.. },
"rule_stats": {}
}
}
},
NooBaa Logs: No error for the fset-bucket6
Jun 16 17:26:07 bl5june-21 node[3735849]: [noobaa-cli/3735849] [L0]core.manage_nsfs.nc_lifecycle:: nc_lifecycle.process_rule: start bucket name: fset-bucket6 rule { filter:
{ prefix: 'file' }, id: 'Expire-file-objects-on-date', status: 'Enabled', expiration: { date: 1741132800000 } } index 0
Jun 16 17:26:07 bl5june-21 node[3735849]: [noobaa-cli/3735849] [L0]core.manage_nsfs.nc_lifecycle:: nc_lifecycle.process_rule: processing rule: fset-bucket6 (bucket id: 6850287288499b0b92d3de2e ) rule { filter:
{ prefix: 'file' }, id: 'Expire-file-objects-on-date', status: 'Enabled', expiration: { date: 1741132800000 } }
Expected results:
Logs collected and log location:
Additional info:
