NO-JIRA: Fix Node NotReady intervals being left open when a node is deleted

[dgoodwin]

Some tests stand up nodes, if they are deleted while not ready, the not
ready intervals stay open until the end of the job, causing a misleading
chart.

[openshift-ci-robot]

@dgoodwin: This pull request explicitly references no jira issue.

In response to this:

Some tests stand up nodes, if they are deleted while not ready, the not
ready intervals stay open until the end of the job, causing a misleading
chart.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[dgoodwin]

/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-techpreview-serial

[openshift-ci]

@dgoodwin: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/d4bc0b10-8432-11f0-86e7-837ca44dbbd3-0

[openshift-ci]

@dgoodwin: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-metal-ipi-virtualmedia	0f822e6	link	false	/test e2e-metal-ipi-virtualmedia
ci/prow/e2e-openstack-ovn	0f822e6	link	false	/test e2e-openstack-ovn
ci/prow/e2e-aws-disruptive	0f822e6	link	false	/test e2e-aws-disruptive
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2	0f822e6	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn-single-node-serial	0f822e6	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade	0f822e6	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-metal-ipi-serial-1of2	0f822e6	link	false	/test e2e-metal-ipi-serial-1of2

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[dgoodwin]

/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-techpreview-serial

[openshift-ci]

@dgoodwin: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.20-e2e-azure-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/44510a20-84c9-11f0-92f3-d8012f2affc5-0

[dgoodwin]

I believe this run now shows the nodes from this test no longer showing NotReady straight to the end of the run. https://sippy.dptools.openshift.org/sippy-ng/job_runs/1961115728765521920/pull-ci-openshift-origin-main-e2e-gcp-ovn-techpreview-serial-2of2/openshift_origin/30188/intervals?end=2025-08-28T20%3A38%3A44Z&filterText=&intervalFile=e2e-timelines_spyglass_20250828-183717.json&overrideDisplayFlag=0&selectedSources=OperatorAvailable&selectedSources=OperatorProgressing&selectedSources=OperatorDegraded&selectedSources=KubeletLog&selectedSources=EtcdLog&selectedSources=EtcdLeadership&selectedSources=Alert&selectedSources=Disruption&selectedSources=E2EFailed&selectedSources=APIServerGracefulShutdown&selectedSources=KubeEvent&selectedSources=NodeState&selectedSources=E2EPassed&start=2025-08-28T18%3A02%3A36Z

[smg247]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dgoodwin, smg247

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dgoodwin,smg247]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment