handle the error case of node retrieval while waiting for reboot

[deads2k]

Fixes

nodes/ failed getting current: resource name may not be empty
nodes/ip-10-0-242-72.us-west-1.compute.internal failed getting current: an error on the server ("read tcp 10.130.4.51:41854->13.56.72.38:6443: read: connection reset by peer") has prevented the request from succeeding (get nodes ip-10-0-242-72.us-west-1.compute.internal)
5 of 7 nodes rebooted, 0 rebooting to desired level: 2023-06-20T15:06:22-07:00

nodes/ failed getting current: resource name may not be empty
nodes/ failed getting current: resource name may not be empty
5 of 7 nodes rebooted, 0 rebooting to desired level: 2023-06-20T15:06:52-07:00

/assign @stlaz

[stlaz]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: deads2k, stlaz

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 [deads2k]

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

[deads2k]

/cherry-pick release-4.13

[openshift-cherrypick-robot]

@deads2k: once the present PR merges, I will cherry-pick it on top of release-4.13 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.13

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/test-infra repository.

[deads2k]

/cherry-pick release-4.12

[deads2k]

/cherry-pick release-4.11

[deads2k]

/cherry-pick release-4.10

[openshift-cherrypick-robot]

@deads2k: once the present PR merges, I will cherry-pick it on top of release-4.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.10

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/test-infra repository.

[openshift-cherrypick-robot]

@deads2k: once the present PR merges, I will cherry-pick it on top of release-4.11 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.11

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/test-infra repository.

[openshift-cherrypick-robot]

@deads2k: once the present PR merges, I will cherry-pick it on top of release-4.12 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.12

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/test-infra repository.

[deads2k]

/override ci/prow/e2e-agnostic-ovn-cmd

[openshift-ci]

@deads2k: Overrode contexts on behalf of deads2k: ci/prow/e2e-agnostic-ovn-cmd

In response to this:

/override ci/prow/e2e-agnostic-ovn-cmd

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/test-infra repository.

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 97651ff and 2 for PR HEAD 614e7e7 in total

[deads2k]

/override ci/prow/e2e-aws-ovn-serial

[openshift-ci]

@deads2k: Overrode contexts on behalf of deads2k: ci/prow/e2e-aws-ovn-serial

In response to this:

/override ci/prow/e2e-aws-ovn-serial

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/test-infra repository.

[openshift-ci]

@deads2k: all tests passed!

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/test-infra repository. I understand the commands that are listed here.

[openshift-cherrypick-robot]

@deads2k: new pull request created: #1484

In response to this:

/cherry-pick release-4.13

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/test-infra repository.

[openshift-cherrypick-robot]

@deads2k: new pull request created: #1485

In response to this:

/cherry-pick release-4.12

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/test-infra repository.

[openshift-cherrypick-robot]

@deads2k: new pull request created: #1486

In response to this:

/cherry-pick release-4.11

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/test-infra repository.

[openshift-cherrypick-robot]

@deads2k: new pull request created: #1487

In response to this:

/cherry-pick release-4.10

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/test-infra repository.