Question

After a network automation job pushes a bulk interface configuration change to a distribution switch, your CI pipeline runs a pyATS verification job. The job log shows: the pre-change snapshot learned 48 interfaces in 'up' state, and the post-change 'Diff' output reports one interface changed from oper_status 'up' to 'down' with no other differences. The intended change was only to update interface descriptions. What should you conclude and do next?

Accepted Answer

The change had an unintended side effect that brought an interface down; treat the pipeline stage as failed and trigger rollback or investigation before promoting the change.

Answer

The pyATS diff is a false positive because description-only changes never affect oper_status; ignore the diff and mark the job passed.

Answer

The learned pre-change snapshot was invalid because pyATS cannot learn oper_status; re-run the job with a CLI show command parser instead.

Answer

The diff indicates a transient learn timing issue; add a longer sleep before the post-change snapshot and re-run to make the diff disappear.