Vlad Lazar e162ab8b53 storcon: handle ongoing deletions gracefully (#9449) ...

## Problem

Pageserver returns 409 (Conflict) if any of the shards are already
deleting the timeline. This resulted in an error being propagated out of
the HTTP handler and to the client. It's an expected scenario so we
should handle it nicely.

This caused failures in `test_storage_controller_smoke`
[here](https://neon-github-public-dev.s3.amazonaws.com/reports/pr-9435/11390431900/index.html#suites/8fc5d1648d2225380766afde7c428d81/86eee4b002d6572d).

## Summary of Changes

Instead of returning an error on 409s, we now bubble the status code up
and let the HTTP handler code retry until it gets a 404 or times out.

2024-10-18 15:33:04 +01:00

..

client

Remove unnecessary dependencies (#9000)

2024-09-17 17:55:45 +03:00

migrations

storcon: track preferred AZ for each tenant shard (#8937)

2024-09-06 13:11:17 +01:00

src

storcon: handle ongoing deletions gracefully (#9449)

2024-10-18 15:33:04 +01:00

Cargo.toml

Rename hyper 1.0 to hyper and hyper 0.14 to hyper0 (#9254)

2024-10-03 16:33:43 +02:00