Skip to content

Fix misleading 'unreachable' log message - #286

Open
cijohnson wants to merge 1 commit into
mainfrom
ichristo/improve_prune_nodes_logging
Open

Fix misleading 'unreachable' log message#286
cijohnson wants to merge 1 commit into
mainfrom
ichristo/improve_prune_nodes_logging

Conversation

@cijohnson

Copy link
Copy Markdown
Collaborator

in pssh.prune_nodes()

The prune_nodes() method was logging all host removals as 'unreachable' even when hosts were pruned for other reasons
(e.g., GID consistency failures, interface validation failures). This was misleading since these hosts were actually reachable over SSH but failed other checks.

Changes:

  • Add optional 'reason' parameter to prune_nodes() (defaults to 'Unreachable')
  • Add optional 'log_pruning' parameter to avoid duplicate logging
  • Update preflight checks to pass specific failure reasons
  • Change preflight summary log level from INFO to WARNING
  • Apply fixes to both single-process and multiprocess Pssh classes

Addresses AIMVT-275: Generic prune_nodes() API should not assume unreachability.

Motivation

Technical Details

Test Plan

Test Result

Submission Checklist

in pssh.prune_nodes()

The prune_nodes() method was logging all host removals as 'unreachable'
even when hosts were pruned for other reasons
(e.g., GID consistency failures, interface validation failures).
This was misleading since these hosts were actually reachable over SSH but failed other checks.

Changes:
- Add optional 'reason' parameter to prune_nodes() (defaults to 'Unreachable')
- Add optional 'log_pruning' parameter to avoid duplicate logging
- Update preflight checks to pass specific failure reasons
- Change preflight summary log level from INFO to WARNING
- Apply fixes to both single-process and multiprocess Pssh classes

Addresses AIMVT-275: Generic prune_nodes() API should not assume unreachability.

Co-authored-by: Cursor <cursoragent@cursor.com>
Signed-off-by: Ignatious Johnson <ichristo@amd.com>
@cijohnson
cijohnson force-pushed the ichristo/improve_prune_nodes_logging branch from 357e57f to 01d3f80 Compare August 3, 2026 23:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant