John Spray a2adc7dbd3 storcon: avoid multiple initdbs when shard 0 has stale locations (#11760) ...

## Problem

In #11727 I overlooked the case of multiple attached locations for shard
0.

I misread the code and thought `create_one` acts on one location, but it
actually acts on one _shard_, which is potentially multiple locations.

This was not a regression, but it meant that the fix was incomplete.

## Summary of changes

- In `create_one`, when updating shard zero, have any "other" locations
use the initdb from shard 0

2025-04-29 15:31:52 +00:00

..

client

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

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

migrations

storage_controller: coordinate imports across shards in the storage controller (#11345)

2025-04-24 11:26:06 +00:00

src

storcon: avoid multiple initdbs when shard 0 has stale locations (#11760)

2025-04-29 15:31:52 +00:00

Cargo.toml

storcon: add https API (#11239)

2025-03-20 08:22:02 +00:00