Skip to content
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

Update Crucible and Propolis to latest #3646

Merged
merged 4 commits into from
Jul 15, 2023
Merged

Conversation

leftwo
Copy link
Contributor

@leftwo leftwo commented Jul 15, 2023

Crucible:
Add quota to agent created datasets (oxidecomputer/crucible#835)

Propolis:
The above crucible changes

Alan Hanson added 3 commits July 15, 2023 14:54
Crucible:
Add quota to agent created datasets (#835)
Switch to building on heliosv2 (#830)
Minor clippy cleanup (#832)
Update to latest dropshot (#829)

Propolis:
The above crucible changes
Switch to building on heliosv2 (#461)
clean up cargo check/clippy errors when built with Rust 1.71 (#462)
Add some VMM_DESTROY_VM polish to bhyve-api
@leftwo
Copy link
Contributor Author

leftwo commented Jul 15, 2023

I may hold this PR and update it once oxidecomputer/propolis#466 lands

@luqmana
Copy link
Contributor

luqmana commented Jul 15, 2023

The failed jobs are because they depend on a helios / package job that failed...but it succeeded? Did the package job get retried? It does look like the job IDs changed 01H5DD08CQ48SHVAVJC94653RP vs 01H5DJ6NJN9SPPGH3K7M9H71QG.

Gonna hit retry for the failed ones

@leftwo
Copy link
Contributor Author

leftwo commented Jul 15, 2023

Yeah, An earlier job (01H5DD08CQ48SHVAVJC94653RP ) failed and I retried it, and completed the 2nd time.

@leftwo
Copy link
Contributor Author

leftwo commented Jul 15, 2023

And, I did pull in later propolis than the original PR had.
This now includes the propolis fix for:

Ubuntu 22.04 guest: "segfault at 10 ip 00007f68a0fd5b41 sp 00007ffc956aa800 error 6 in libc.so.6" during first boot

Propolis issue #427

@leftwo leftwo merged commit 76658a1 into main Jul 15, 2023
@leftwo leftwo deleted the alan/cru-and-prop-together-again branch July 15, 2023 21:52
@iliana iliana mentioned this pull request Jul 16, 2023
iliana added a commit that referenced this pull request Jul 16, 2023
1. Moving the zones onto the U.2 devices (#3557), real or synthetic,
results in the paths of all the zones changing, which results in the
paths of all their logs changing. Updated the deploy.sh job to look in
the new spot for logs, so that we can find:
2. The end-to-end test is failing[^1] because Nexus is returning a 500
on disk creation, because [Nexus cannot contact the Crucible
downstairs](https://buildomat.eng.oxide.computer/wg/0/artefact/01H5ED4P9ZPW22RMY4BEDV0X6Q/VZmMOazlZARWMoMr6qgqt59i4NHEwei5lZ4Ds8d5TJLKdbd2/01H5ED53S5T9XSX4PXS7K6GZ1S/01H5EGRG8XW9GWBQ6ZQXP93WPD/oxide-nexus:default.log?format=x-bunyan#L3759),
because [the Crucible agent is repeatedly panicking because it cannot
create a dataset, because the zpool is out of
space](https://buildomat.eng.oxide.computer/wg/0/artefact/01H5ED4P9ZPW22RMY4BEDV0X6Q/VZmMOazlZARWMoMr6qgqt59i4NHEwei5lZ4Ds8d5TJLKdbd2/01H5ED53S5T9XSX4PXS7K6GZ1S/01H5EGRF4V6N2XS8TXN2B6CK15/oxide-crucible-agent:default.log?format=x-bunyan#L93).
We attempt to rectify the issue by increasing the size of the synthetic
drives in create_virtual_hardware.sh.
3. It is possible that we are hitting this limit for the first time
because Crucible as of #3646 reserves more space.

(We should also switch the deploy job to using real disks, instead of
tmpfs, for these datasets. But that will not be part of this PR.)

[^1]: Not always; some commits are evidently lucky.
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.

2 participants