You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a system where I've never installed Omicron, I ran destroy_virtual_hardware.sh (which I think is supposed to be idempotent):
dap@ivanova omicron-deploy $ pfexec ./tools/destroy_virtual_hardware.sh
+++ dirname ./tools/destroy_virtual_hardware.sh
++ cd ./tools
++ pwd
+ SOURCE_DIR=/home/dap/omicron-deploy/tools
+ cd /home/dap/omicron-deploy/tools/..
+ OMICRON_TOP=/home/dap/omicron-deploy
+ MARKER=/etc/opt/oxide/NO_INSTALL
+ [[ -f /etc/opt/oxide/NO_INSTALL ]]
++ id -u
+ [[ 0 -ne 0 ]]
+ try_remove_vnics
+ try_remove_address lo0/underlay
+ local ADDRESS=lo0/underlay
+ RC=0
++ ipadm show-addr -p -o addr lo0/underlay
ipadm: Address object not found+ [[ -n '' ]]
+ [[ 0 -eq 0 ]]
+ success 'Address lo0/underlay destroyed'
+ echo -e '\e[1;36mAddress lo0/underlay destroyed\e[0m'
Address lo0/underlay destroyed
+ VNIC_LINKS=("net0" "net1")
+ for LINK in "${VNIC_LINKS[@]}"
+ try_remove_vnic net0
+ local LINK=net0
+ RC=0
++ dladm show-vnic -p -o LINK net0
dladm: invalid vnic name 'net0': object not found
+ [[ -n '' ]]
+ [[ 0 -eq 0 ]]
+ success 'VNIC link net0 destroyed'
+ echo -e '\e[1;36mVNIC link net0 destroyed\e[0m'
VNIC link net0 destroyed
+ for LINK in "${VNIC_LINKS[@]}"
+ try_remove_vnic net1
+ local LINK=net1
+ RC=0
++ dladm show-vnic -p -o LINK net1
dladm: invalid vnic name 'net1': object not found
+ [[ -n '' ]]
+ [[ 0 -eq 0 ]]
+ success 'VNIC link net1 destroyed'
+ echo -e '\e[1;36mVNIC link net1 destroyed\e[0m'
VNIC link net1 destroyed
+ try_destroy_zpools
+ readarray -t ZPOOLS
++ zfs list -d 0 -o name
++ grep '^oxp_'
There are a bunch of error-looking messages in there and it's not super clear whether things are okay in the current state. (I gather that they are. The two kinds of messages here are reporting things are destroyed that actually never existed and reporting that certain objects are not found that it would have removed anyway. But it's not obvious this is okay unless you already know what this script does and how.)
The text was updated successfully, but these errors were encountered:
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]>
On a system where I've never installed Omicron, I ran
destroy_virtual_hardware.sh
(which I think is supposed to be idempotent):There are a bunch of error-looking messages in there and it's not super clear whether things are okay in the current state. (I gather that they are. The two kinds of messages here are reporting things are destroyed that actually never existed and reporting that certain objects are not found that it would have removed anyway. But it's not obvious this is okay unless you already know what this script does and how.)
The text was updated successfully, but these errors were encountered: