oxidecomputer / oxidecomputer/omicron

`oxide system hardware switch list` returns empty list

Open
#6,394 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

api networking
Dominant language
Rust
Stars
572
Forks
97
Avg merge
2d 12h
Merged PRs (30d)
96

Description

I am running a4x2 with the following combination of commits:

  • omicron 6dd980251a26430466bcd5aff1edad5416cf94e5
  • maghemite 242e67e1e6b363b9bae04c90920fb8f43ac0a51d
  • oxnet 7dacd265f1bcd0f8b47bd4805250c4f0812da206

I am using the version of the Oxide CLI from https://github.com/oxidecomputer/oxide.rs/pull/795, with commit 6fbbd5568289e95432ed7adfb6808c3d3cd0e3f0:

$ oxide version
Oxide CLI 0.6.1+20240710.0
Built from commit: 6fbbd5568289e95432ed7adfb6808c3d3cd0e3f0 
Oxide API: 20240821.0

I ran the following command, and I was hoping to see values like switch0 and switch1, but I instead got an empty list.

$ oxide system hardware switch list
[]

I ran this command, but I don't understand the difference between switch_location and switch, and whether switch_location should appear in the output of the above command.

$ oxide system hardware switch-port list
[
  {
    "id": "<omitted>3761",
    "port_name": "qsfp1",
    "rack_id": "51becb40-1818-4ea0-b278-2af26bc8bbe4",
    "switch_location": "switch0"
  }, {
    "id": "<omitted>a494",
    "port_name": "qsfp0",
    "port_settings_id": "<omitted>6760",
    "rack_id": "51becb40-1818-4ea0-b278-2af26bc8bbe4",
    "switch_location": "switch0"
  }, {
    "id": "<omitted>f319",
    "port_name": "qsfp0",
    "port_settings_id": "<omitted>1775",
    "rack_id": "51becb40-1818-4ea0-b278-2af26bc8bbe4",
    "switch_location": "switch1"
  }, {
    "id": "<omitted>a6e1",
    "port_name": "qsfp1",
    "rack_id": "51becb40-1818-4ea0-b278-2af26bc8bbe4",
    "switch_location": "switch1"
  }

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce oxide system hardware switch list using the Omicron, Maghemite, Oxnet, and Oxide CLI commits listed in the report. Compare its empty result with oxide system hardware switch-port list, focusing on how switch and switch_location are represented. Done when the command returns the expected switch values or the discrepancy is clearly documented and covered by an appropriate test.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
api
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.