Skip to content

Remove bonus Volume layer#1927

Merged
jmpesp merged 2 commits into
oxidecomputer:mainfrom
jmpesp:no_double_voluming
Apr 22, 2026
Merged

Remove bonus Volume layer#1927
jmpesp merged 2 commits into
oxidecomputer:mainfrom
jmpesp:no_double_voluming

Conversation

@jmpesp

@jmpesp jmpesp commented Apr 21, 2026

Copy link
Copy Markdown
Contributor

Volume::construct was unintentionally adding another layer of Volume when constructing from a request. Remove this, ensuring that what is constructed matches the request.

`Volume::construct` was unintentionally adding another layer of Volume
when constructing from a request. Remove this, ensuring that what is
constructed matches the request.
@jmpesp jmpesp requested review from leftwo and mkeeter April 21, 2026 16:53

@leftwo leftwo left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I assume (as tests pass) that the volume replacement stuff can still handle and we did not accidentally require multiple volume layers to make things work?

Also, this should not impact what Omicron has in the json blob for a VCR, right?

@jmpesp

jmpesp commented Apr 21, 2026

Copy link
Copy Markdown
Contributor Author

I assume (as tests pass) that the volume replacement stuff can still handle and we did not accidentally require multiple volume layers to make things work?

If anything it's a testament to our code quality that the replacement code worked before and after this change :) I have the same fear here too, but will also trust the tests here.

Also, this should not impact what Omicron has in the json blob for a VCR, right?

I also had this same fear, but no: the request that's stored in the database doesn't change or need to change here. It's Volume::construct's interpretation of the request that is changing.

Comment thread upstairs/src/volume.rs
}
}

fn to_arc_block_io<T>(b: T) -> Arc<dyn BlockIO + Send + Sync>

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm mad that this is necessary (and that we can't use Arc::new or .from() directly), but haven't found a way to avoid it.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

😢

Comment thread upstairs/src/guest.rs Outdated
(guest, io)
}

pub async fn create_and_up_main(

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This function doesn't need async (clippy complains in my editor, dunno why it passes in CI)

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks, did that in ae5f3ee

@jmpesp

jmpesp commented Apr 22, 2026

Copy link
Copy Markdown
Contributor Author

I spun up the Canada region and performed a bunch of replacements, so we're good here. Going to merge!

@jmpesp jmpesp merged commit 784aeb7 into oxidecomputer:main Apr 22, 2026
17 checks passed
@jmpesp jmpesp deleted the no_double_voluming branch April 22, 2026 21:50
jmpesp added a commit to oxidecomputer/omicron that referenced this pull request May 26, 2026
Update Crucible from `7103cd3a` to `bd9a0e2a`, picking up the following
PRs:

- Use an explicit rev for oxidecomputer git deps
(oxidecomputer/crucible#1936)
- Add Clone and Deserialize to VolumeInfo et al
(oxidecomputer/crucible#1935)
- Update omicron/oximeter (oxidecomputer/crucible#1933)
- [meta] update to drift 0.1.4 (oxidecomputer/crucible#1932)
- Don't log if there is nothing to log (oxidecomputer/crucible#1930)
- Add VolumeInfo (oxidecomputer/crucible#1928)
- Remove bonus Volume layer (oxidecomputer/crucible#1927)
- Add session and client id to panic messages
(oxidecomputer/crucible#1926)
- [crucible-agent-types] migrate to RFD 619 pattern
(oxidecomputer/crucible#1899)
- Background read-only region creation (oxidecomputer/crucible#1919)
- [crucible-downstairs-repair] switch to RFD 619 pattern
(oxidecomputer/crucible#1901)
- [crucible-pantry] switch to RFD 619 pattern
(oxidecomputer/crucible#1900)
- Use separate in-memory types (oxidecomputer/crucible#1913)
- Remove old field from dtrace action script
(oxidecomputer/crucible#1917)
- Retry data writes that return an IO error
(oxidecomputer/crucible#1915)
- Bump dropshot to 0.17.0 (oxidecomputer/crucible#1909)
- Reject snapshot requests when read-only (oxidecomputer/crucible#1914)
- update ringbuf method, fix clippy lint (oxidecomputer/crucible#1904)
- bump vergen-v9 version too (oxidecomputer/crucible#1903)
- update dropshot to 0.16.7, dropshot-api-manager to 0.5.2
(oxidecomputer/crucible#1851)
- perf-vol.d updates (oxidecomputer/crucible#1898)
- upgrade progenitor to 0.13, reqwest to 0.13
(oxidecomputer/crucible#1854)
- Remove cargo nextest from github workflow, out of space
(oxidecomputer/crucible#1846)
- Add a test for VCR serialize/deserialize (oxidecomputer/crucible#1843)

Update Propolis from `bc489ddf` to `58ab73bd`, picking up the following
PRs:

- Bump crucible to latest, update Omicron, use explicit revs
(oxidecomputer/propolis#1141)
- Add project and silo ids to VM attestation
(oxidecomputer/propolis#1114)
- Update escargot (oxidecomputer/propolis#1139)
- Prefix shebang and mark D scripts as executable
(oxidecomputer/propolis#1140)
- Fix error in propolis-server README (oxidecomputer/propolis#1138)
- [meta] update to drift 0.1.4 (oxidecomputer/propolis#1137)
- Fix Intel CPUID leaf 4 cache topology for SMT
(oxidecomputer/propolis#1002)
- support NVMe Deallocate (oxidecomputer/propolis#1105)
- viona: do not lose used/avail indices (oxidecomputer/propolis#1135)
- viona: multiqueue device should stay multiqueue across migration
(oxidecomputer/propolis#1121)
- Bump crucible rev to latest (oxidecomputer/propolis#1132)
- expand zerocopy IntoBytes/FromByes use in guest memory accesses
(oxidecomputer/propolis#1130)
- dropshot-api-manager 0.7.1 (oxidecomputer/propolis#1129)
- improve slog component setting (oxidecomputer/propolis#1124)
- wait for viona Poller to run before declaring device running
(oxidecomputer/propolis#1118)
- virtio: tolerate importing queues with adjusted size
(oxidecomputer/propolis#1117)
- Run viona unit tests in CI (oxidecomputer/propolis#1120)
- feature gate Crucible-specific boot digest code
(oxidecomputer/propolis#1119)

Also:

- ran `cargo update -p vergen`

- removed the `reqwest012` dependency

- removed `reqwest012_client` from Nexus

- ran `cargo hakari generate` and `cargo hakari manage-deps`

- replace use of `ProgenitorOperationRetry` with
`retry_operation_while_indefinitely`

- during the region replacement drive saga, consume the new `VolumeInfo`
from Propolis and use that to determine when to consider a replacement
done
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants