Bug: Fix processing invalidation of DIDs different than files

[juanpablosalas]

Bug Description

The issue arises in the cronjobs that process the file invalidation jobs. They can correctly parse invalidations at the file level and mark their status as "success" but fail to do the same for datasets and containers.

Reproduction Steps

1. Send an invalidation request with a dataset/container
2. The status in the API will be stuck in "in_progress" although it will already be invalidated

Expected Behavior

Change the status to "success" for invalidated datasets/containers.

Possible Solution

Adjust the logic behind

CMSRucio/DMOps/file_invalidation_server/fi_manager/process_jobs.py

Line 103 in e4861f5

if dbs_invalidated_dataset:

Related Issues

No response