John Spray b7173b1ef0 storcon: fix case where we might fail to send compute notifications after two opposite migrations (#9435) ...

## Problem

If we migrate A->B, then B->A, and the notification of A->B fails, then
we might have retained state that makes us think "A" is the last state
we sent to the compute hook, whereas when we migrate B->A we should
really be sending a fresh notification in case our earlier failed
notification has actually mutated the remote compute config.

Closes: #9417 

## Summary of changes

- Add a reproducer for the bug
(`test_storage_controller_compute_hook_revert`)
- Refactor compute hook code to represent remote state with
`ComputeRemoteState` which stores a boolean for whether the compute has
fully applied the change as well as the request that the compute
accepted.
- The actual bug fix: after sending a compute notification, if we got a
423 response then update our ComputeRemoteState to reflect that we have
mutated the remote state. This way, when we later try and notify for our
historic location, we will properly see that as a change and send the
notification.

Co-authored-by: Vlad Lazar <vlad@neon.tech>

2024-10-18 11:29:23 +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: fix case where we might fail to send compute notifications after two opposite migrations (#9435)

2024-10-18 11:29:23 +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