REQ 015

REQ-015: Post-restart WinRM readiness via a real round-trip, not bare TCP

Requirement

After restarting a Windows LabVIEW guest, the pipeline shall confirm WinRM readiness via a real WinRM round-trip request, not merely a successful TCP connection to the WinRM port.

Rationale

A bare TCP-port check was observed live to report ready while the SOAP/PowerShell-remoting service was not yet actually able to handle requests, causing a ReadTimeoutError on the very next real command.

Fit Criterion

provision-windows-labview-vm.yml's "Attach Installer Media And Restart" step polls provision-windows-guest.py ... wait-ready (a real WinRM call) in a retry loop, and explicitly fails the step (rather than silently exhausting retries and reporting success) if readiness is never reached.

Verification

Code review; the step's own inline comment documents the earlier, more confusing failure mode this specifically replaced.

Source

Software-Requirements-Specification

Priority

High

TestID

TEST-015

TestArtifact

Code review; documented live ReadTimeoutError finding this replaced

CodeRef

vm/windows-labview/provision-windows-guest.py wait-ready command

Status

Verified (manual)