Skip to content
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

[release-4.14] OCPBUGS-19087,OCPBUGS-19905: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp #1879

Merged

Conversation

dcbw
Copy link
Contributor

@dcbw dcbw commented Sep 16, 2023

Includes the following relevant changes:

Includes the following relevant changes:

- LoadBalancer incremental processing to reduce CPU usage in
Service-heavy scenarios
[https://issues.redhat.com/browse/OCPBUGS-19004]

- Always CT commit ECMP traffic in original direction to reduce
OVS CPU usage in benchmark testing
[https://issues.redhat.com/browse/OCPBUGS-19010]
@dcbw dcbw changed the title [release-4.14] Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp [release-4.14] OCPBUGS-19087: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp Sep 16, 2023
@openshift-ci-robot openshift-ci-robot added jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Sep 16, 2023
@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Jira Issue OCPBUGS-19087, which is invalid:

  • expected the bug to target the "4.15.0" version, but it targets "4.14.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Includes the following relevant changes:

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 openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 16, 2023
@dcbw dcbw changed the base branch from master to release-4.14 September 16, 2023 14:28
@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Jira Issue OCPBUGS-19087, which is invalid:

  • expected dependent Jira Issue OCPBUGS-19010 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Includes the following relevant changes:

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 16, 2023

/jira refresh

@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Jira Issue OCPBUGS-19087, which is invalid:

  • expected dependent Jira Issue OCPBUGS-19010 to be in one of the following states: MODIFIED, ON_QA, VERIFIED, but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 17, 2023

/retest-required

@dcbw
Copy link
Contributor Author

dcbw commented Sep 17, 2023

/test okd-e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 17, 2023

@dcbw: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-local-gateway
  • /test e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upgrade-local-gateway
  • /test e2e-aws-ovn-windows
  • /test e2e-gcp-ovn
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere-windows
  • /test gofmt
  • /test images
  • /test lint
  • /test unit

The following commands are available to trigger optional jobs:

  • /test e2e-aws-ovn-hypershift
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-azure-ovn
  • /test e2e-metal-ipi-ovn-ipv4
  • /test e2e-openstack-ovn
  • /test e2e-ovn-hybrid-step-registry
  • /test e2e-vsphere-ovn
  • /test qe-perfscale-aws-ovn-medium-cluster-density
  • /test qe-perfscale-aws-ovn-medium-node-density-cni
  • /test qe-perfscale-aws-ovn-small-cluster-density
  • /test qe-perfscale-aws-ovn-small-node-density-cni

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-hypershift
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-kubevirt
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-gateway
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-serial
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade-local-gateway
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-windows
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-azure-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-gcp-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-openstack-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-ovn-hybrid-step-registry
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-vsphere-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-vsphere-windows
  • pull-ci-openshift-ovn-kubernetes-release-4.14-gofmt
  • pull-ci-openshift-ovn-kubernetes-release-4.14-images
  • pull-ci-openshift-ovn-kubernetes-release-4.14-lint
  • pull-ci-openshift-ovn-kubernetes-release-4.14-unit

In response to this:

/test okd-e2e-gcp-ovn

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 17, 2023

/test ci/prow/okd-e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 17, 2023

@dcbw: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

  • /test e2e-aws-ovn
  • /test e2e-aws-ovn-local-gateway
  • /test e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • /test e2e-aws-ovn-serial
  • /test e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • /test e2e-aws-ovn-upgrade
  • /test e2e-aws-ovn-upgrade-local-gateway
  • /test e2e-aws-ovn-windows
  • /test e2e-gcp-ovn
  • /test e2e-metal-ipi-ovn-dualstack
  • /test e2e-metal-ipi-ovn-ipv6
  • /test e2e-vsphere-windows
  • /test gofmt
  • /test images
  • /test lint
  • /test unit

The following commands are available to trigger optional jobs:

  • /test e2e-aws-ovn-hypershift
  • /test e2e-aws-ovn-kubevirt
  • /test e2e-azure-ovn
  • /test e2e-metal-ipi-ovn-ipv4
  • /test e2e-openstack-ovn
  • /test e2e-ovn-hybrid-step-registry
  • /test e2e-vsphere-ovn
  • /test qe-perfscale-aws-ovn-medium-cluster-density
  • /test qe-perfscale-aws-ovn-medium-node-density-cni
  • /test qe-perfscale-aws-ovn-small-cluster-density
  • /test qe-perfscale-aws-ovn-small-node-density-cni

Use /test all to run the following jobs that were automatically triggered:

  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-hypershift
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-kubevirt
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-gateway
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-local-to-shared-gateway-mode-migration
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-serial
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-shared-to-local-gateway-mode-migration
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-upgrade-local-gateway
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-aws-ovn-windows
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-azure-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-gcp-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-dualstack
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-metal-ipi-ovn-ipv6
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-openstack-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-ovn-hybrid-step-registry
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-vsphere-ovn
  • pull-ci-openshift-ovn-kubernetes-release-4.14-e2e-vsphere-windows
  • pull-ci-openshift-ovn-kubernetes-release-4.14-gofmt
  • pull-ci-openshift-ovn-kubernetes-release-4.14-images
  • pull-ci-openshift-ovn-kubernetes-release-4.14-lint
  • pull-ci-openshift-ovn-kubernetes-release-4.14-unit

In response to this:

/test ci/prow/okd-e2e-gcp-ovn

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/jira refresh

@openshift-ci-robot openshift-ci-robot added the jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. label Sep 19, 2023
@openshift-ci-robot
Copy link
Contributor

@dcbw: This pull request references Jira Issue OCPBUGS-19087, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.14.0) matches configured target version for branch (4.14.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
  • dependent bug Jira Issue OCPBUGS-19010 is in the state MODIFIED, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-19010 targets the "4.15.0" version, which is one of the valid target versions: 4.15.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

In response to this:

/jira refresh

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 openshift-ci-robot removed the jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. label Sep 19, 2023
@dcbw dcbw added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. and removed jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 19, 2023
@jcaamano
Copy link
Contributor

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Sep 19, 2023
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dcbw, jcaamano

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@anuragthehatter
Copy link

/label cherry-pick-approved

@openshift-ci openshift-ci bot added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 19, 2023
@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/okd-e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Cannot get PR #1879 in openshift/ovn-kubernetes

In response to this:

/override ci/prow/okd-e2e-gcp-ovn

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/tide refresh

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/okd-e2e-gcp-ovn

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/okd-e2e-gcp-ovn

In response to this:

/override ci/prow/okd-e2e-gcp-ovn

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
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 495fe5a and 2 for PR HEAD d597385 in total

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/retest-required

AWS: insufficient capacity

2023-09-19T15:28:43Z 1x kubelet: Error: kubelet may be retrying requests that are timing out in CRI-O due to system load. Currently at stage container storage creation: context deadline exceeded: error reserving ctr name k8s_inject-cli_e2e-vsphere-windows-ipi-install-install_ci-op-d4kgw2vp_b866c898-73a1-48e7-8abc-0ef6d789b187_0 for id 4206b2f7bf1b66efa57819a38aa7317237333cd90f950e5e3d5c3ad4e3f3779d: name is reserved
* 2023-09-19T15:38:33Z 1x kubelet: Failed to inspect image "image-registry.openshift-image-registry.svc:5000/ci-op-d4kgw2vp/stable@sha256:65414ff5fac8b2680d327e4842dc054744a1e62c543a9b1f547c24b36b22070f": rpc error: code = DeadlineExceeded desc = context deadline exceeded

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/e2e-aws-ovn

timed out during deprovision

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

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

In response to this:

/override ci/prow/e2e-aws-ovn

timed out during deprovision

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/e2e-metal-ipi-ovn-dualstack

{ static pod lifecycle failure - static pod: "kube-controller-manager" in namespace: "openshift-kube-controller-manager" for revision: 5 on node: "master-1.ostest.test.metalkube.org" didn't show up, waited: 3m0s}

is unrelated to networking; kubelet appears to churn the pod and its installer pod between 15:38:00 and 15:40:00

Sep 19 15:40:02.561364 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:02.561325    4814 mirror_client.go:138] "Failed deleting a mirror pod" err="Timeout: request did not complete within requested timeout - context deadline exceeded" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org"
Sep 19 15:40:02.690513 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:02.690491    4814 kubelet.go:1911] "Trying to delete pod" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" podUID=30c83c4b-d02b-4ae0-a996-ea08a69bb781
Sep 19 15:40:02.690513 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:02.690512    4814 mirror_client.go:130] "Deleting a mirror pod" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" podUID=30c83c4b-d02b-4ae0-a996-ea08a69bb781
Sep 19 15:40:06.069750 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:06.069742    4814 kubelet_getters.go:187] "Pod status updated" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" status=Running
Sep 19 15:40:25.174015 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:25.173924    4814 event.go:280] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"kube-controller-manager-guard-master-1.ostest.test.metalkube.org.178656f5bba3a780", GenerateName:"", Namespace:"openshift-kube-controller-manager", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Pod", Namespace:"openshift-kube-controller-manager", Name:"kube-controller-manager-guard-master-1.ostest.test.metalkube.org", UID:"16c61daa-0e00-47ea-a841-253203f4ac9f", APIVersion:"v1", ResourceVersion:"14156", FieldPath:"spec.containers{guard}"}, Reason:"ProbeError", Message:"Readiness probe error: Get \"https://192.168.111.21:10257/healthz\": dial tcp 192.168.111.21:10257: connect: connection refused\nbody: \n", Source:v1.EventSource{Component:"kubelet", Host:"master-1.ostest.test.metalkube.org"}, FirstTimestamp:time.Date(2023, time.September, 19, 15, 38, 43, 166611328, time.Local), LastTimestamp:time.Date(2023, time.September, 19, 15, 38, 48, 167081281, time.Local), Count:2, Type:"Warning", EventTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'Timeout: request did not complete within requested timeout - context deadline exceeded' (will not retry!)
Sep 19 15:40:36.692292 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:36.692248    4814 mirror_client.go:138] "Failed deleting a mirror pod" err="Timeout: request did not complete within requested timeout - context deadline exceeded" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org"
Sep 19 15:40:43.852124 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:43.851887    4814 kubelet.go:2457] "SyncLoop (PLEG): event for pod" pod="openshift-kube-controller-manager-operator/kube-controller-manager-operator-65856598c9-7klf9" event=&{ID:41577366-8759-4ca2-9b82-7106cb6bf343 Type:ContainerDied Data:34190b966d56028e8632937419f0435701adb354e5caaccad45489bb42d6d16b}
Sep 19 15:40:43.852574 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:43.852554    4814 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-controller-manager-operator\" with CrashLoopBackOff: \"back-off 10s restarting failed container=kube-controller-manager-operator pod=kube-controller-manager-operator-65856598c9-7klf9_openshift-kube-controller-manager-operator(41577366-8759-4ca2-9b82-7106cb6bf343)\"" pod="openshift-kube-controller-manager-operator/kube-controller-manager-operator-65856598c9-7klf9" podUID=41577366-8759-4ca2-9b82-7106cb6bf343

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/e2e-metal-ipi-ovn-dualstack

In response to this:

/override ci/prow/e2e-metal-ipi-ovn-dualstack

{ static pod lifecycle failure - static pod: "kube-controller-manager" in namespace: "openshift-kube-controller-manager" for revision: 5 on node: "master-1.ostest.test.metalkube.org" didn't show up, waited: 3m0s}

is unrelated to networking; kubelet appears to churn the pod and its installer pod between 15:38:00 and 15:40:00

Sep 19 15:40:02.561364 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:02.561325    4814 mirror_client.go:138] "Failed deleting a mirror pod" err="Timeout: request did not complete within requested timeout - context deadline exceeded" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org"
Sep 19 15:40:02.690513 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:02.690491    4814 kubelet.go:1911] "Trying to delete pod" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" podUID=30c83c4b-d02b-4ae0-a996-ea08a69bb781
Sep 19 15:40:02.690513 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:02.690512    4814 mirror_client.go:130] "Deleting a mirror pod" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" podUID=30c83c4b-d02b-4ae0-a996-ea08a69bb781
Sep 19 15:40:06.069750 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:06.069742    4814 kubelet_getters.go:187] "Pod status updated" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org" status=Running
Sep 19 15:40:25.174015 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:25.173924    4814 event.go:280] Server rejected event '&v1.Event{TypeMeta:v1.TypeMeta{Kind:"", APIVersion:""}, ObjectMeta:v1.ObjectMeta{Name:"kube-controller-manager-guard-master-1.ostest.test.metalkube.org.178656f5bba3a780", GenerateName:"", Namespace:"openshift-kube-controller-manager", SelfLink:"", UID:"", ResourceVersion:"", Generation:0, CreationTimestamp:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), DeletionTimestamp:<nil>, DeletionGracePeriodSeconds:(*int64)(nil), Labels:map[string]string(nil), Annotations:map[string]string(nil), OwnerReferences:[]v1.OwnerReference(nil), Finalizers:[]string(nil), ManagedFields:[]v1.ManagedFieldsEntry(nil)}, InvolvedObject:v1.ObjectReference{Kind:"Pod", Namespace:"openshift-kube-controller-manager", Name:"kube-controller-manager-guard-master-1.ostest.test.metalkube.org", UID:"16c61daa-0e00-47ea-a841-253203f4ac9f", APIVersion:"v1", ResourceVersion:"14156", FieldPath:"spec.containers{guard}"}, Reason:"ProbeError", Message:"Readiness probe error: Get \"https://192.168.111.21:10257/healthz\": dial tcp 192.168.111.21:10257: connect: connection refused\nbody: \n", Source:v1.EventSource{Component:"kubelet", Host:"master-1.ostest.test.metalkube.org"}, FirstTimestamp:time.Date(2023, time.September, 19, 15, 38, 43, 166611328, time.Local), LastTimestamp:time.Date(2023, time.September, 19, 15, 38, 48, 167081281, time.Local), Count:2, Type:"Warning", EventTime:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Series:(*v1.EventSeries)(nil), Action:"", Related:(*v1.ObjectReference)(nil), ReportingController:"", ReportingInstance:""}': 'Timeout: request did not complete within requested timeout - context deadline exceeded' (will not retry!)
Sep 19 15:40:36.692292 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:36.692248    4814 mirror_client.go:138] "Failed deleting a mirror pod" err="Timeout: request did not complete within requested timeout - context deadline exceeded" pod="openshift-kube-controller-manager/kube-controller-manager-master-1.ostest.test.metalkube.org"
Sep 19 15:40:43.852124 master-1.ostest.test.metalkube.org kubenswrapper[4814]: I0919 15:40:43.851887    4814 kubelet.go:2457] "SyncLoop (PLEG): event for pod" pod="openshift-kube-controller-manager-operator/kube-controller-manager-operator-65856598c9-7klf9" event=&{ID:41577366-8759-4ca2-9b82-7106cb6bf343 Type:ContainerDied Data:34190b966d56028e8632937419f0435701adb354e5caaccad45489bb42d6d16b}
Sep 19 15:40:43.852574 master-1.ostest.test.metalkube.org kubenswrapper[4814]: E0919 15:40:43.852554    4814 pod_workers.go:1300] "Error syncing pod, skipping" err="failed to \"StartContainer\" for \"kube-controller-manager-operator\" with CrashLoopBackOff: \"back-off 10s restarting failed container=kube-controller-manager-operator pod=kube-controller-manager-operator-65856598c9-7klf9_openshift-kube-controller-manager-operator(41577366-8759-4ca2-9b82-7106cb6bf343)\"" pod="openshift-kube-controller-manager-operator/kube-controller-manager-operator-65856598c9-7klf9" podUID=41577366-8759-4ca2-9b82-7106cb6bf343

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration

Deprovision timed out

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration

In response to this:

/override ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration

Deprovision timed out

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

/override ci/prow/e2e-aws-ovn-upgrade-local-gateway
/override ci/prow/e2e-aws-ovn-upgrade

deprovision timed out

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Overrode contexts on behalf of dcbw: ci/prow/e2e-aws-ovn-upgrade, ci/prow/e2e-aws-ovn-upgrade-local-gateway

In response to this:

/override ci/prow/e2e-aws-ovn-upgrade-local-gateway
/override ci/prow/e2e-aws-ovn-upgrade

deprovision failed

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.

@dcbw
Copy link
Contributor Author

dcbw commented Sep 19, 2023

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

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: Overrode contexts on behalf of dcbw: 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
Copy link
Contributor

openshift-ci bot commented Sep 19, 2023

@dcbw: 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-vsphere-ovn d597385 link false /test e2e-vsphere-ovn
ci/prow/e2e-openstack-ovn d597385 link false /test e2e-openstack-ovn
ci/prow/e2e-azure-ovn d597385 link false /test e2e-azure-ovn
ci/prow/e2e-aws-ovn-serial d597385 link unknown /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-upgrade d597385 link unknown /test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration d597385 link unknown /test e2e-aws-ovn-local-to-shared-gateway-mode-migration
ci/prow/e2e-aws-ovn d597385 link unknown /test e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack d597385 link unknown /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-upgrade-local-gateway d597385 link unknown /test e2e-aws-ovn-upgrade-local-gateway

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-merge-robot openshift-merge-robot merged commit e563872 into openshift:release-4.14 Sep 19, 2023
27 of 29 checks passed
@openshift-ci-robot
Copy link
Contributor

@dcbw: Jira Issue OCPBUGS-19087: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-19087 has been moved to the MODIFIED state.

In response to this:

Includes the following relevant changes:

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-merge-robot
Copy link
Contributor

Fix included in accepted release 4.14.0-0.nightly-2023-09-20-033502

@dcbw dcbw changed the title [release-4.14] OCPBUGS-19087: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp [release-4.14] OCPBUGS-19087, OCPBUGS-19905: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp Sep 28, 2023
@openshift-ci-robot
Copy link
Contributor

@dcbw: Jira Issue OCPBUGS-19905 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Includes the following relevant changes:

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.

@dcbw dcbw changed the title [release-4.14] OCPBUGS-19087, OCPBUGS-19905: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp [release-4.14] OCPBUGS-19087,OCPBUGS-19905: Dockerfile: bump OVN to ovn23.09-23.09.0-beta.31.el9fdp Sep 28, 2023
@openshift-ci-robot
Copy link
Contributor

@dcbw: Jira Issue OCPBUGS-19087 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

Jira Issue OCPBUGS-19905 is in an unrecognized state (ON_QA) and will not be moved to the MODIFIED state.

In response to this:

Includes the following relevant changes:

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet