-
Notifications
You must be signed in to change notification settings - Fork 58
Description
I was using a4x2 with:
- omicron 02303a6
- Oxide CLI from branch in Commands for managing bgp auth and route local preference oxide.rs#795 commit
98f000bfc68b375e49888ff6946ffa988092084e
with merge from Adapt to LLDP-related changes in link APIs oxide.rs#808 commit457db93dc13a09d45df09597dd0a3c1becd0b086
, resolved merge conflicts by hand.
I tried to add/set (add has been renamed to set) a bgp peer that I already deleted previously (so the bgp peer did not exist at the time), but at add/set time I supplied a bad UUID for the --bgp-config
flag value, where the UUID supplied had the last digit increased by 1 from the real UUID value. It accepted the bad value with no complaints.
$ oxide system networking bgp peer set --rack 2d1fe615-0fd9-485d-8898-cd024883d222 --switch switch1 --port qsfp0 --addr 169.254.40.1 --bgp-config c722f444-9e03-4c07-8a58-89ed53c43dd6
This command then panicked when trying to show the bgp peers (and static route) for switch1/qsfp0
:
$ oxide system networking switch-port-settings show
switch0/qsfp0
=============
Autoneg Fec Speed
false None Speed100G
Address Lot VLAN
169.254.10.2/30 initial-infra None
169.254.30.2/30 initial-infra None
BGP Peer Config Export Import Communities Connect Retry Delay Open Enforce First AS Hold Time Idle Hold Time Keepalive Local Pref Md5 Auth Min TTL MED Remote ASN VLAN
169.254.10.1 as65547 [no filtering] [no filtering] [] 3 3 false 6 0 2 None None None None None None
169.254.30.1 as65547 [no filtering] [no filtering] [] 3 3 false 6 0 2 None None None None None None
Destination Nexthop Vlan Preference
switch1/qsfp0
=============
Autoneg Fec Speed
false None Speed100G
Address Lot VLAN
169.254.20.2/30 initial-infra None
169.254.40.2/30 initial-infra None
thread 'tokio-runtime-worker' panicked at cli/src/cmd_net.rs:1292:61:
no entry found for key
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'main' panicked at cli/src/main.rs:109:10:
called `Result::unwrap()` on an `Err` value: JoinError::Panic(Id(129), ...)
The current workaround is to just overwrite with correct UUID.
$ oxide system networking bgp peer set --rack 2d1fe615-0fd9-485d-8898-cd024883d222 --switch switch1 --port qsfp0 --addr 169.254.40.1 --bgp-config c722f444-9e03-4c07-8a58-89ed53c43dd5
Output is ok after the workaround:
$ oxide system networking switch-port-settings show
switch0/qsfp0
=============
Autoneg Fec Speed
false None Speed100G
Address Lot VLAN
169.254.10.2/30 initial-infra None
169.254.30.2/30 initial-infra None
BGP Peer Config Export Import Communities Connect Retry Delay Open Enforce First AS Hold Time Idle Hold Time Keepalive Local Pref Md5 Auth Min TTL MED Remote ASN VLAN
169.254.10.1 as65547 [no filtering] [no filtering] [] 3 3 false 6 0 2 None None None None None None
169.254.30.1 as65547 [no filtering] [no filtering] [] 3 3 false 6 0 2 None None None None None None
Destination Nexthop Vlan Preference
switch1/qsfp0
=============
Autoneg Fec Speed
false None Speed100G
Address Lot VLAN
169.254.20.2/30 initial-infra None
169.254.40.2/30 initial-infra None
BGP Peer Config Export Import Communities Connect Retry Delay Open Enforce First AS Hold Time Idle Hold Time Keepalive Local Pref Md5 Auth Min TTL MED Remote ASN VLAN
169.254.20.1 as65547 [no filtering] [no filtering] [] 3 3 false 6 3 2 None None None None None None
Destination Nexthop Vlan Preference
240.0.0.0/4 169.254.30.1/32 0 10
Metadata
Metadata
Assignees
Labels
networkingRelated to the networking.Related to the networking.