Skip to content

[action] [PR:4584] [BMC] Align is_bmc_supported check for the new infra#385

Merged
mssonicbld merged 1 commit into
Azure:202608from
mssonicbld:cherry/msft-202608/4584
Jul 1, 2026
Merged

[action] [PR:4584] [BMC] Align is_bmc_supported check for the new infra#385
mssonicbld merged 1 commit into
Azure:202608from
mssonicbld:cherry/msft-202608/4584

Conversation

@mssonicbld

Copy link
Copy Markdown
Collaborator

What I did

The BMC support check in generate_dump was aligned with the new infrastructure flow
(sonic-net/sonic-buildimage#26544).
Instead of checking for platform-local bmc.json assumptions, the logic now validates host-side role and runtime BMC data from the canonical source used by the system.

How I did it

  • Updated generate_dump BMC detection to use device_info.is_switch_host() together with
    device_info.get_bmc_data().
  • Removed reliance on legacy platform-folder bmc.json existence behavior for this path.
  • Kept the generate_dump flow behavior intact while aligning detection to runtime
    /etc/sonic/bmc.json-based APIs.

How to verify it

  • Run show techsupport (or generate_dump) on:
    • a switch-host platform with valid BMC data and verify BMC-related flow executes.
    • a non-switch-host / missing-BMC-data platform and verify BMC path is skipped.

Signed-off-by: Sonic Build Admin sonicbld@microsoft.com

Previous command output (if the output of a command-line utility has changed)

New command output (if the output of a command-line utility has changed)

<!--
    Please make sure you've read and understood our contributing guidelines:
    https://github.com/Azure/SONiC/blob/gh-pages/CONTRIBUTING.md

    ** Make sure all your commits include a signature generated with `git commit -s` **

    If this is a bug fix, make sure your description includes "closes #xxxx",
    "fixes #xxxx" or "resolves #xxxx" so that GitHub automatically closes the related
    issue when the PR is merged.

    If you are adding/modifying/removing any command or utility script, please also
    make sure to add/modify/remove any unit tests from the tests
    directory as appropriate.

    If you are modifying or removing an existing 'show', 'config' or 'sonic-clear'
    subcommand, or you are adding a new subcommand, please make sure you also
    update the Command Line Reference Guide (doc/Command-Reference.md) to reflect
    your changes.

    Please provide the following information:
-->

#### What I did
The BMC support check in `generate_dump` was aligned with the new infrastructure flow
(sonic-net/sonic-buildimage#26544).
Instead of checking for platform-local `bmc.json` assumptions, the logic now validates host-side role and runtime BMC data from the canonical source used by the system.

#### How I did it
- Updated `generate_dump` BMC detection to use `device_info.is_switch_host()` together with
  `device_info.get_bmc_data()`.
- Removed reliance on legacy platform-folder `bmc.json` existence behavior for this path.
- Kept the `generate_dump` flow behavior intact while aligning detection to runtime
  `/etc/sonic/bmc.json`-based APIs.

#### How to verify it
- Run `show techsupport` (or `generate_dump`) on:
  - a switch-host platform with valid BMC data and verify BMC-related flow executes.
  - a non-switch-host / missing-BMC-data platform and verify BMC path is skipped.

Signed-off-by: Sonic Build Admin <sonicbld@microsoft.com>

#### Previous command output (if the output of a command-line utility has changed)

#### New command output (if the output of a command-line utility has changed)
@mssonicbld

Copy link
Copy Markdown
Collaborator Author

Original PR: sonic-net/sonic-utilities#4584

@mssonicbld

Copy link
Copy Markdown
Collaborator Author

/azp run

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@mssonicbld mssonicbld merged commit 111995d into Azure:202608 Jul 1, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant