Repository navigation
Fix per-node bootflash sizing in mixed-version fabrics - #494
Merged
Merged
Conversation
Collaborator
Author
Integration test summary —
|
…-per-node-bootflash
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Switches already running split-image releases were sized using the fabric's lowest switch version, causing false bootflash failures in mixed-version fabrics. Use each node's
fabricNode.versionandfirmwareRunning.ksFile, joined by(pod, node), to select the current architecture. Nodes at/after 6.0(2a) require twice their matching target image size (or one copy when downloaded), without requiring their installed image in the Firmware Repository.The six-node #493 reproducer now requires 5389.46 MiB and passes with ~6489–6502 MiB available. Missing node version/architecture is listed for manual evaluation; confirmed space failures remain failures. Existing pre-boundary/crossing formulas and target-image availability checks are retained. #490's separate capacity/predownload redesign is intentionally excluded.
Fixes #493.
Validation (local Python 3.12, no live integration):
git diff --check: passed.Environment notes: default Python 3.15 is incompatible with the existing threading test harness; Python 3.12 was used. An initial full-suite attempt stopped at collection because
jinja2was unavailable; the proportionate suites above completed successfully.