-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
test failure: "Failed to find a type oid for ..." #1219
Comments
The key error seems to be:
|
This looks like a failure while setting up the sled agent server. The string omicron/sled-agent/src/sim/storage.rs Lines 223 to 241 in 0b11803
This function is public, but it has only one callsite: omicron/sled-agent/src/sim/sled_agent.rs Lines 120 to 127 in 0b11803
Which is almost certainly being invoked by: omicron/nexus/test-utils/src/resource_helpers.rs Lines 350 to 376 in 0b11803
The caller side seems "correct" here - this code path is doing what it's supposed to do, AFAICT. However, that error message implies to me that CRDB is either:
|
Here's the diesel error:
omicron/common/src/sql/dbinit.sql Lines 135 to 139 in 0b11803
And managed in Rust as this type: omicron/nexus/src/db/model/dataset_kind.rs Lines 10 to 23 in 0b11803
|
Due to the "copy-from-seed-db" behavior, which should be initialized with the |
I ran into something similar again:
|
interesting data point, that the "not found" oid changed ( |
Both are created |
And |
Yet another one:
It seems to be more common lately. That's surprising because I haven't updated my omicron commit. I'm on 095dfb6, which is nearly 236f2ac (the tip of "main" on May 27). I have recently changed to a custom CockroachDB build, but that was only Friday (after this bug was filed) and all that's changed is using malloc(3c) for the memory allocator. |
It's conceivable that this is caused by the same underlying illumos issue described in #1146. I'm not sure how we can know this unless we (1) see this again using a cockroach binary without that fix and grab a core file from CockroachDB, or (2) see this again at all once the bug is fixed. |
Propolis changes: Add `IntrPin::import_state` and migrate LPC UART pin states (#669) Attempt to set WCE for raw file backends Fix clippy/lint nits for rust 1.77.0 Crucible changes: Correctly (and robustly) count bytes (#1237) test-replay.sh fix name of DTrace script (#1235) BlockReq -> BlockOp (#1234) Simplify `BlockReq` (#1218) DTrace, cmon, cleanup, retry downstairs connections at 10 seconds. (#1231) Remove `MAX_ACTIVE_COUNT` flow control system (#1217) Crucible changes that were in Omicron but not in Propolis before this commit. Return *410 Gone* if volume is inactive (#1232) Update Rust crate opentelemetry to 0.22.0 (#1224) Update Rust crate base64 to 0.22.0 (#1222) Update Rust crate async-recursion to 1.1.0 (#1221) Minor cleanups to extent implementations (#1230) Update Rust crate http to 0.2.12 (#1220) Update Rust crate reedline to 0.30.0 (#1227) Update Rust crate rayon to 1.9.0 (#1226) Update Rust crate nix to 0.28 (#1223) Update Rust crate async-trait to 0.1.78 (#1219) Various buffer optimizations (#1211) Add low-level test for message encoding (#1214) Don't let df failures ruin the buildomat tests (#1213) Activate the NBD server's psuedo file (#1209) --------- Co-authored-by: Alan Hanson <[email protected]>
While trying to repro #1130, I ran into a failure I hadn't seen before and can't find a ticket for:
Log file:
The text was updated successfully, but these errors were encountered: