Prevent gRRPC's BackupStatus from canceling pending futures

[rzvoncek]

Fixes #742.

Prior to this patch, I could even reproduce the exception from the issue in the integration tests:

[2024-04-11 13:17:02,362] INFO: Registered backup id grpc_backup_23
[2024-04-11 13:17:02,363] INFO: Recording async backup information.
[2024-04-11 13:17:02,363] ERROR: Exception in callback record_backup_info(<Future cancelled>) at /Users/zvo/github/cassandra-medusa/medusa/service/grpc/server.py:346
handle: <Handle record_backup_info(<Future cancelled>) at /Users/zvo/github/cassandra-medusa/medusa/service/grpc/server.py:346>
Traceback (most recent call last):
  File "/Users/zvo/anaconda3/lib/python3.11/asyncio/events.py", line 80, in _run
    self._context.run(self._callback, *self._args)
  File "/Users/zvo/github/cassandra-medusa/medusa/service/grpc/server.py", line 349, in record_backup_info
    if future.exception():
       ^^^^^^^^^^^^^^^^^^
asyncio.exceptions.CancelledError: Removal of backup requested. Cancelling backup Name: grpc_backup_23 with done state: False

[burmanm]

question: In which case is the overwrite_existing=True and is_async=True ? I can't find such invocation in current codebase so I was wondering is the overwrite_existing=False intended to be used only with async cases?

[smutel]

Hello,

I have the same issue. Do you have any workaround to suggest me ? The backups seems completely hanged ...

Thanks.

[adejanovski]

One logging is inaccurate now and I would like to understand why we're re-registering backups when checking their status.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud