NSFS | S3 | Lifecycle: Invalid rule status returns http error 500

[nhaustein]

Environment info

• NooBaa Version: noobaa-core-5.17.1-20241104.el9.x86_64
• Platform: RHEL 9.2 x86

Actual behavior

1. When posting a lifecycle rule with Status=enabled instead of Status=Enabled, Noobaa returns status 500. Here is an example of the policy:

{
"Rules": [
{
"ID": "Expiration-simple",
"Status": "enabled",
"Filter": {
"Prefix": "small"
},
"Expiration": { "Days": 20 }
}
]
}

Here is the status code from the aws cli debug response
2024-11-21 17:25:40,746 - MainThread - botocore.parsers - DEBUG - Response body:
b'InternalErrorWe encountered an internal error. Please try again./files?lifecyclem3rixim4-hnhpv-1102'
2024-11-21 17:25:40,748 - MainThread - botocore.hooks - DEBUG - Event needs-retry.s3.PutBucketLifecycleConfiguration: calling handler <botocore.retryhandler.RetryHandler object at 0x7fd7d7f07760>
2024-11-21 17:25:40,748 - MainThread - botocore.retryhandler - DEBUG - retry needed: retryable HTTP status code received: 500

Expected behavior

1. Invalid status should return 400 (bad request) instead of 500 (internal server error)

Steps to reproduce

1. Use the lifecycle rule above.

More information - Screenshots / Logs / Other output