Skip to content

[DownstreamMerge] 4 -28-22 completed pods#1065

Closed
trozet wants to merge 15 commits intoopenshift:masterfrom
trozet:merge-4-28-completed-pods
Closed

[DownstreamMerge] 4 -28-22 completed pods#1065
trozet wants to merge 15 commits intoopenshift:masterfrom
trozet:merge-4-28-completed-pods

Conversation

@trozet
Copy link
Contributor

@trozet trozet commented Apr 30, 2022

based on @zshi-redhat merge with only the completed pod fixes

oribon and others added 15 commits April 26, 2022 11:04
* Add boilerplate file to fix *-gen commands: `Failed loading boilerplate: open : no such file or directory`.

Signed-off-by: Ori Braunshtein <obraunsh@redhat.com>
Adding the API necessary for the EgressQoS controller
implementation as described in openshift/enhancements#1035

Signed-off-by: Ori Braunshtein <obraunsh@redhat.com>
Add the EgressQoS controller as described in openshift/enhancements#1035

Signed-off-by: Ori Braunshtein <obraunsh@redhat.com>
Signed-off-by: Ori Braunshtein <obraunsh@redhat.com>
the assumption here is that the key/cert files are pre-generated and
mounted into the ovnkube container (running either as a master or node)
and paths for these files are exposed using OVNKUBE_METRICS_PK and
OVNKUBE_METRICS_CERT environment variables

Signed-off-by: Girish Moodalbail <gmoodalbail@nvidia.com>
a correctly configured noHostSubnet node will never become avalible on
GCP because the unavailable condition will never be cleared.

Signed-off-by: Jacob Tanenbaum <jtanenba@redhat.com>
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
When SBDB Chassis rows are deleted, remove the associated
ChassisPrivate row as well.

Remove stale ChassisPrivate rows on initial node synchronization.

Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
This is avoid data plane down time during ovn-controller upgrade.

See ovn-org/ovn@896adfd

Signed-off-by: Han Zhou <hzhou@ovn.org>
call clearInitialNodeNetworkUnavailableCondition for noHostSubnet nodes
The nested allocator calls were propagating an error type up during an
IP release. However in the bitmap allocator function it was never
possible to error during an IP release. Remove the return type.

Signed-off-by: Tim Rozet <trozet@redhat.com>
(cherry picked from commit 1a430bc)
Changes-Include:
 - During pod sync we allocate IPs of all existing pods, but we should
   ignore completed pods
 - During namespace add we add all of the pod IPs to the ns address set,
   but we should ignore completed pods
 - During processing of delete event for a completed pod, we were trying
   to delete the pod again, which would try to free the IP that was
   previously released and could be in use by another pod. We should
   ignore delete events for completed resources as they would have been
   handled during update.
 - On node add, we add all existing pods on that node back to retry as
   an "add". We should skip completed pods here.
 - We now check during deletion of a completed pod (should happen on
   update only) to make sure no other running pods are using this IP as
   a failsafe to ensure we never release an IP in use by another pod or
   the related OVN config

Signed-off-by: Tim Rozet <trozet@redhat.com>
(cherry picked from commit 7bcc8da)
Upon fetching all of the NATs on a router, if the NATs or the router
dont exist this should not be an error for deletion.

Signed-off-by: Tim Rozet <trozet@redhat.com>
(cherry picked from commit 8ad0d79)
@openshift-ci openshift-ci bot requested review from JacobTanenbaum and squeed April 30, 2022 14:43
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 30, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: trozet

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

The pull request process is described here

Details 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2022
@tssurya
Copy link
Contributor

tssurya commented May 1, 2022

It's happening in this merge request:

2022-04-30T17:11:44.674Z|00803|binding|INFO|Mismatch iface-id-ver for lport e2e-statefulset-9558_ss-0, expected 67ec61d5-1f1b-4c9e-98bd-b5d9e9803435, found 9874984a-ffd7-4ecf-bbf2-873062cddbb7

@openshift-ci openshift-ci bot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 3, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 3, 2022

@trozet: PR needs rebase.

Details

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.

@squeed
Copy link
Contributor

squeed commented Jul 18, 2022

/uncc

@openshift-ci openshift-ci bot removed the request for review from squeed July 18, 2022 04:31
@zshi-redhat
Copy link
Contributor

this one can be closed in favor of #1064 ?

@openshift-bot
Copy link
Contributor

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Oct 21, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 12, 2022

@trozet: 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-gcp-ovn aa4b054 link true /test e2e-gcp-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack aa4b054 link true /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-ovn-upgrade-local-gateway aa4b054 link true /test e2e-aws-ovn-upgrade-local-gateway
ci/prow/e2e-aws-ovn-local-to-shared-gateway-mode-migration aa4b054 link true /test e2e-aws-ovn-local-to-shared-gateway-mode-migration
ci/prow/4.11-upgrade-from-stable-4.10-local-gateway-e2e-aws-ovn-upgrade aa4b054 link false /test 4.11-upgrade-from-stable-4.10-local-gateway-e2e-aws-ovn-upgrade
ci/prow/okd-e2e-gcp-ovn aa4b054 link false /test okd-e2e-gcp-ovn
ci/prow/4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade aa4b054 link true /test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-local-gateway aa4b054 link true /test e2e-aws-ovn-local-gateway
ci/prow/e2e-aws-ovn-shared-to-local-gateway-mode-migration aa4b054 link true /test e2e-aws-ovn-shared-to-local-gateway-mode-migration
ci/prow/e2e-azure-ovn aa4b054 link false /test e2e-azure-ovn
ci/prow/e2e-aws-ovn-upgrade aa4b054 link true /test e2e-aws-ovn-upgrade
ci/prow/lint aa4b054 link true /test lint
ci/prow/unit aa4b054 link true /test unit
ci/prow/gofmt aa4b054 link true /test gofmt
ci/prow/4.12-upgrade-from-stable-4.11-images aa4b054 link true /test 4.12-upgrade-from-stable-4.11-images
ci/prow/4.12-upgrade-from-stable-4.11-local-gateway-images aa4b054 link true /test 4.12-upgrade-from-stable-4.11-local-gateway-images
ci/prow/4.13-upgrade-from-stable-4.12-e2e-aws-ovn-upgrade aa4b054 link true /test 4.13-upgrade-from-stable-4.12-e2e-aws-ovn-upgrade
ci/prow/4.13-upgrade-from-stable-4.12-local-gateway-e2e-aws-ovn-upgrade aa4b054 link true /test 4.13-upgrade-from-stable-4.12-local-gateway-e2e-aws-ovn-upgrade
ci/prow/4.13-upgrade-from-stable-4.12-images aa4b054 link true /test 4.13-upgrade-from-stable-4.12-images
ci/prow/4.13-upgrade-from-stable-4.12-local-gateway-images aa4b054 link true /test 4.13-upgrade-from-stable-4.12-local-gateway-images

Full PR test history. Your PR dashboard.

Details

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.

@zshi-redhat
Copy link
Contributor

/close

@openshift-ci openshift-ci bot closed this Nov 14, 2022
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 14, 2022

@zshi-redhat: Closed this PR.

Details

In response to this:

/close

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. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD.

Projects

None yet

Development

Successfully merging this pull request may close these issues.