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

Bug 1959058: policy: release LSP lock before adding pods to default-deny portgroups. #529

Merged
merged 1 commit into from May 10, 2021

Conversation

squeed
Copy link
Contributor

@squeed squeed commented May 10, 2021

Profiling indicated a lot of contention on this lock. We should release
it before we commit our changes to OVN.

Signed-off-by: Casey Callendrello cdc@redhat.com

This is a backport of ovn-org/ovn-kubernetes#2205

Profiling indicated a lot of contention on this lock. We should release
it before we commit our changes to OVN.

Signed-off-by: Casey Callendrello <cdc@redhat.com>
@squeed squeed requested a review from trozet May 10, 2021 15:14
@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 10, 2021
@dcbw
Copy link
Contributor

dcbw commented May 10, 2021

/lgtm

@dcbw
Copy link
Contributor

dcbw commented May 10, 2021

@squeed needs a bug though

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label May 10, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@squeed squeed changed the title policy: release LSP lock before adding pods to default-deny portgroups. Bug 1950283: policy: release LSP lock before adding pods to default-deny portgroups. May 10, 2021
@openshift-ci openshift-ci bot added the bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. label May 10, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: This pull request references Bugzilla bug 1950283, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.0) matches configured target release for branch (4.8.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @mffiedler

In response to this:

Bug 1950283: policy: release LSP lock before adding pods to default-deny portgroups.

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 bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label May 10, 2021
@openshift-ci openshift-ci bot requested a review from mffiedler May 10, 2021 16:17
@squeed squeed changed the title Bug 1950283: policy: release LSP lock before adding pods to default-deny portgroups. Bug 1959058: policy: release LSP lock before adding pods to default-deny portgroups. May 10, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: This pull request references Bugzilla bug 1959058, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.0) matches configured target release for branch (4.8.0)
  • bug is in the state NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (anusaxen@redhat.com), skipping review request.

In response to this:

Bug 1959058: policy: release LSP lock before adding pods to default-deny portgroups.

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 bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. and removed bugzilla/severity-urgent Referenced Bugzilla bug's severity is urgent for the branch this PR is targeting. labels May 10, 2021
@squeed
Copy link
Contributor Author

squeed commented May 10, 2021

/bugzilla refresh

@openshift-ci openshift-ci bot removed the bugzilla/severity-unspecified Referenced Bugzilla bug's severity is unspecified for the PR. label May 10, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: This pull request references Bugzilla bug 1959058, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.8.0) matches configured target release for branch (4.8.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (anusaxen@redhat.com), skipping review request.

In response to this:

/bugzilla 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 openshift-ci bot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label May 10, 2021
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@squeed
Copy link
Contributor Author

squeed commented May 10, 2021

/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-aws-ovn-windows
they're broken.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: Overrode contexts on behalf of squeed: ci/prow/e2e-aws-ovn-windows, ci/prow/e2e-vsphere-ovn

In response to this:

/override ci/prow/e2e-vsphere-ovn
/override ci/prow/e2e-aws-ovn-windows
they're broken.

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

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

2 similar comments
@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@dcbw
Copy link
Contributor

dcbw commented May 10, 2021

ovn-upgrade failure is synthetic test issues that are being fixed by ensuring pods don't schedule while network plugin is upgraded
dual-stack failure is the server has received too many requests and has asked us to try again later (get builds.build.openshift.io)
vsphere is either terraform failing to download the install image because of dial tcp: lookup releases-art-rhcos.svc.ci.openshift.org on 172.30.0.10:53: no such host or problems setting up the cluster-bot RBAC long before networking

/retest

@openshift-bot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade ec1af35 link /test 4.8-upgrade-from-stable-4.7-e2e-aws-ovn-upgrade
ci/prow/e2e-gcp-ovn-upgrade ec1af35 link /test e2e-gcp-ovn-upgrade
ci/prow/okd-e2e-gcp-ovn ec1af35 link /test okd-e2e-gcp-ovn
ci/prow/e2e-vsphere-ovn ec1af35 link /test e2e-vsphere-ovn

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

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit b386fc1 into openshift:master May 10, 2021
@openshift-ci
Copy link
Contributor

openshift-ci bot commented May 10, 2021

@squeed: All pull requests linked via external trackers have merged:

Bugzilla bug 1959058 has been moved to the MODIFIED state.

In response to this:

Bug 1959058: policy: release LSP lock before adding pods to default-deny portgroups.

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. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. 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

4 participants