OCPBUGS-62359: Check more operatorsProgressing #30367
Conversation
openshift-ci-robot
added
jira/valid-reference
|
@weliang1: This pull request references Jira Issue OCPBUGS-62359, which is valid. The bug has been moved to the POST state. 3 validation(s) were run on this bug
No GitHub users were found matching the public email listed for the QA contact in Jira (weliang@redhat.com), skipping review request. The bug has been updated to refer to the pull request using the external bug tracker. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: weliang1 The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-ovn-upgrade-network-flow-matrix |
|
@weliang1: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/b92f45b0-a5fc-11f0-9823-b60a2bec6e25-0 |
|
/payload-job periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6 |
|
@weliang1: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c02a88c0-a5fc-11f0-8cf2-a96b5ce62d12-0 |
|
/payload-job periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade |
|
@weliang1: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c5f5b040-a5fc-11f0-967d-4427ac442cc0-0 |
|
/payload-job periodic-ci-openshift-release-master-ci-4.20-e2e-vsphere-runc-upgrade |
|
@weliang1: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/cc111aa0-a5fc-11f0-909f-092b64e4a11b-0 |
|
/retest |
|
@weliang1: 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-sigs/prow repository. I understand the commands that are listed here. |
2 participants
OCPBUGS-62359 failed for different reasons across multiple test runs
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-ovn-upgrade-network-flow-matrix/1971288846830145536
dial tcp: lookup api-int.ostest.test.metalkube.org on 192.168.111.1:53: no such host
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.20-upgrade-from-stable-4.19-e2e-metal-ipi-upgrade-ovn-ipv6/1970880061380759552
dial tcp: lookup api-int.ostest.test.metalkube.org on [fd2e:6f44:5dd8:c956::1]:53: no such host
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-e2e-azure-ovn-upgrade/1975088922878808064
SetNetworkStatus: failed to update the pod prometheus-k8s-1 in out of cluster comm: status update failed for pod openshift-monitoring/prometheus-k8s-1: etcdserver: request timed out
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-e2e-vsphere-runc-upgrade/1971834599860342784
etNetworkStatus: failed to update the pod alertmanager-main-1 in out of cluster comm: status update failed for pod /: Get "https://api-int.ci-op-rky0hgt1-3e3a9.vmc-ci.devcluster.openshift.com:6443/api/v1/namespaces/openshift-monitoring/pods/alertmanager-main-1?timeout=1m0s": http2: client connection force closed via ClientConn.Close
Pod sandbox creation in OpenShift follows this sequence: kubelet → CRI (crio/containerd) → CNI (Multus + OVN-Kubernetes). Any disruption in this chain during cluster's upgrading, such as node restarts, CNI/OVN outages, or API lookups used by the CNI, can result in a FailedCreatePodSandBox error.
Added checks for DNS, etcd and kube-apiserver health during pod creation to filter sandbox creation failures during upgrades.