-
Notifications
You must be signed in to change notification settings - Fork 130
gocli: Add wait for cri-o service to be ready after proxy settings applied #1303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gocli: Add wait for cri-o service to be ready after proxy settings applied #1303
Conversation
…plied There was previously a wait for the cri-o service to be ready[1] after applying the docker proxy settings but this was not included with the introduction of the opts package[2]. This can lead to kubeadm failing its preflight checks as cri-o is not ready[3] [1] https://github.com/kubevirt/kubevirtci/blob/03aa94e9da974b0e37dc8f180a4f700d47020c08/cluster-provision/k8s/1.31/nodes.sh#L43 [2] kubevirt#1217 [3] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/13020/pull-kubevirt-e2e-k8s-1.31-sig-network/1843292337933914112#1:build-log.txt%3A343 Signed-off-by: Brian Carey <bcarey@redhat.com>
8621b1c
to
593a277
Compare
Signed-off-by: Brian Carey <bcarey@redhat.com>
593a277
to
f1606f9
Compare
/lgtm |
/override check-up-kind-sriov see #1305 |
@brianmcarey: Overrode contexts on behalf of brianmcarey: check-up-kind-sriov In response to this:
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. |
@xpivarc - check-provisions have passed here |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: xpivarc 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:
Approvers can indicate their approval by writing |
/override check-up-kind-sriov |
@brianmcarey: Overrode contexts on behalf of brianmcarey: check-up-kind-sriov In response to this:
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. |
@brianmcarey: The following test failed, say
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. |
/override check-provision-k8s-1.30 No tests failed - the lane timed out. It has already passed against this PR. |
@brianmcarey: Overrode contexts on behalf of brianmcarey: check-provision-k8s-1.30 In response to this:
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. |
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
[1cedd17 gocli: Add wait for cri-o service to be ready after proxy settings applied](kubevirt/kubevirtci#1303) [0f94b65 Automatic bump of CentOS Stream to latest](kubevirt/kubevirtci#1292) ```release-note NONE ``` Signed-off-by: kubevirt-bot <kubevirtbot@redhat.com>
What this PR does / why we need it:
There was previously a wait for the cri-o service to be ready[1] after applying the docker proxy settings but this was not included with the introduction of the opts package[2].
This can lead to kubeadm failing its preflight checks as cri-o is not ready[3]
[1]
kubevirtci/cluster-provision/k8s/1.31/nodes.sh
Line 43 in 03aa94e
[2] #1217
[3] https://prow.ci.kubevirt.io/view/gs/kubevirt-prow/pr-logs/pull/kubevirt_kubevirt/13020/pull-kubevirt-e2e-k8s-1.31-sig-network/1843292337933914112#1:build-log.txt%3A343
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Special notes for your reviewer:
/cc @aerosouund @xpivarc
Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.
Release note: