434-dynamically-calculate-the-required-free-space-in-switch-bootflash - #441
lovkeshsharma702 wants to merge 21 commits into
Conversation
monrog2
left a comment
There was a problem hiding this comment.
Requesting changes for several cases where the new dynamic calculation can report PASS despite insufficient bootflash. Each item is documented inline with a concrete remediation and regression-test expectation.
monrog2
left a comment
There was a problem hiding this comment.
@lovkeshsharma702 I am requesting these two blocking changes. Both can produce a false PASS during the documented APIC-first upgrade sequence or after an image has been downloaded but still needs extraction.
Ensure bootflash validation reports the established target-version message before checking switch-version availability, with focused regression coverage. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Distinguish pre-split and split-image upgrade scenarios, credit only the staged 32-bit image during boundary crossings, and document the API-based calculations. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Summarize what the dynamic bootflash check validates and update the stale sample result message. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Describe the cleanup threshold, dynamic image-space calculation, downloaded-image handling, and validation outcomes without exposing implementation detail. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Integration test summaryIntegration testing was run across the actual fabric versions and six configured upgrade paths. Python 2.7 and Python 3.8 unit tests passed. For the Switch Node
Example complete check hit, with fabric identifiers scrubbed and the updated recommendation: |
cover dynamic space check.