Alex Chi Z. f3ef60d236 fix(storcon): use unified interface to handle 404 lsn lease (#12650) ...

## Problem

Close LKB-270. This is part of our series of efforts to make sure
lsn_lease API prompts clients to retry. Follow up of
https://github.com/neondatabase/neon/pull/12631.

Slack thread w/ Vlad:
https://databricks.slack.com/archives/C09254R641L/p1752677940697529

## Summary of changes

- Use `tenant_remote_mutation` API for LSN leases. Makes it consistent
with new APIs added to storcon.
- For 404, we now always retry because we know the tenant is
to-be-attached and will eventually reach a point that we can find that
tenant on the intent pageserver.
- Using the `tenant_remote_mutation` API also prevents us from the case
where the intent pageserver changes within the lease request. The
wrapper function will error with 503 if such things happen.

---------

Signed-off-by: Alex Chi Z <chi@neon.tech>

2025-07-18 04:40:35 +00:00

..

client

storcon + safekeeper + scrubber: propagate root CA certs everywhere (#11418)

2025-04-04 06:30:48 +00:00

migrations

A few more SC changes (#12649)

2025-07-17 23:17:01 +00:00

src

fix(storcon): use unified interface to handle 404 lsn lease (#12650)

2025-07-18 04:40:35 +00:00

Cargo.toml

A few SC changes (#12615)

2025-07-17 13:14:36 +00:00