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.

Sign up for GitHub

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

Jump to bottom

SDN-4930: Add host isolation mounts to ovnkube-node #2591

Merged
merged 1 commit into from
Jan 16, 2025
Merged

SDN-4930: Add host isolation mounts to ovnkube-node #2591

merged 1 commit into from
Jan 16, 2025
+26 −0

Conversation

jcaamano
Copy link
Contributor

No description provided.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Dec 11, 2024
@npinaeva npinaeva mentioned this pull request Dec 13, 2024
Closed
@jcaamano
Copy link
Contributor Author

/retest

@npinaeva
Copy link
Member

/lgtm
tested with dev-scripts and ovn-kubernetes/ovn-kubernetes#4930

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Dec 23, 2024
@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Dec 23, 2024

[APPROVALNOTIFIER] This PR is APPROVED

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

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

@tssurya
Copy link
Contributor

tssurya commented Jan 9, 2025

/label acknowledge-critical-fixes-only

@openshift-ci openshift-ci bot added the acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. label Jan 9, 2025
@tssurya
Copy link
Contributor

tssurya commented Jan 9, 2025 •
edited by openshift-ci bot
Loading

/retitle SDN-4930: Add host isolation mounts to ovnkube-node

@openshift-ci openshift-ci bot changed the title Add host isolation mounts to ovnkube-node SDN-4930: Add host isolation mounts to ovnkube-node Jan 9, 2025
@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jan 9, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 9, 2025 •
edited by openshift-ci bot
Loading

@jcaamano: This pull request references SDN-4930 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the epic to target either version "4.19." or "openshift-4.19.", but it targets "openshift-4.18" instead.

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.

@tssurya
Copy link
Contributor

tssurya commented Jan 9, 2025

/test

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 9, 2025

@tssurya: The /test command needs one or more targets.
The following commands are available to trigger required jobs:

/test 4.18-upgrade-from-stable-4.17-images

/test e2e-aws-ovn-hypershift-conformance

/test e2e-aws-ovn-upgrade

/test e2e-aws-ovn-windows

/test e2e-azure-ovn-upgrade

/test e2e-gcp-ovn

/test e2e-gcp-ovn-techpreview

/test e2e-gcp-ovn-upgrade

/test e2e-metal-ipi-ovn-ipv6

/test e2e-metal-ipi-ovn-ipv6-ipsec

/test e2e-ovn-ipsec-step-registry

/test images

/test lint

/test unit

/test verify

The following commands are available to trigger optional jobs:

/test 4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

/test 4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade

/test 4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-upgrade

/test e2e-aws-hypershift-ovn-kubevirt

/test e2e-aws-ovn-ipsec-serial

/test e2e-aws-ovn-ipsec-upgrade

/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-single-node

/test e2e-aws-ovn-techpreview-serial

/test e2e-azure-ovn

/test e2e-azure-ovn-dualstack

/test e2e-azure-ovn-manual-oidc

/test e2e-network-mtu-migration-ovn-ipv4

/test e2e-network-mtu-migration-ovn-ipv6

/test e2e-openstack-ovn

/test e2e-ovn-hybrid-step-registry

/test e2e-ovn-step-registry

/test e2e-vsphere-ovn

/test e2e-vsphere-ovn-dualstack

/test e2e-vsphere-ovn-dualstack-primaryv6

/test e2e-vsphere-ovn-windows

/test frrk8s-e2e

/test okd-scos-e2e-aws-ovn

/test okd-scos-images

/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

/test security

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

pull-ci-openshift-cluster-network-operator-master-4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-4.18-upgrade-from-stable-4.17-e2e-gcp-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-4.18-upgrade-from-stable-4.17-images

pull-ci-openshift-cluster-network-operator-master-e2e-aws-hypershift-ovn-kubevirt

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-hypershift-conformance

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-local-to-shared-gateway-mode-migration

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-serial

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-shared-to-local-gateway-mode-migration

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-single-node

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-e2e-aws-ovn-windows

pull-ci-openshift-cluster-network-operator-master-e2e-azure-ovn

pull-ci-openshift-cluster-network-operator-master-e2e-azure-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn

pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn-techpreview

pull-ci-openshift-cluster-network-operator-master-e2e-gcp-ovn-upgrade

pull-ci-openshift-cluster-network-operator-master-e2e-metal-ipi-ovn-ipv6

pull-ci-openshift-cluster-network-operator-master-e2e-metal-ipi-ovn-ipv6-ipsec

pull-ci-openshift-cluster-network-operator-master-e2e-network-mtu-migration-ovn-ipv4

pull-ci-openshift-cluster-network-operator-master-e2e-network-mtu-migration-ovn-ipv6

pull-ci-openshift-cluster-network-operator-master-e2e-openstack-ovn

pull-ci-openshift-cluster-network-operator-master-e2e-ovn-hybrid-step-registry

pull-ci-openshift-cluster-network-operator-master-e2e-ovn-ipsec-step-registry

pull-ci-openshift-cluster-network-operator-master-e2e-ovn-step-registry

pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn

pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack

pull-ci-openshift-cluster-network-operator-master-e2e-vsphere-ovn-dualstack-primaryv6

pull-ci-openshift-cluster-network-operator-master-images

pull-ci-openshift-cluster-network-operator-master-lint

pull-ci-openshift-cluster-network-operator-master-okd-scos-e2e-aws-ovn

pull-ci-openshift-cluster-network-operator-master-security

pull-ci-openshift-cluster-network-operator-master-unit

pull-ci-openshift-cluster-network-operator-master-verify

In response to this:

/test

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.

@tssurya
Copy link
Contributor

tssurya commented Jan 9, 2025

/cherry-pick release-4.18

@openshift-cherrypick-robot
Copy link

@tssurya: once the present PR merges, I will cherry-pick it on top of release-4.18 in a new PR and assign it to you.

In response to this:

/cherry-pick release-4.18

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 9d96bcc and 2 for PR HEAD 69a1624 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 1 for PR HEAD 69a1624 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

2 similar comments
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

@tssurya
Copy link
Contributor

tssurya commented Jan 13, 2025

/test e2e-azure-ovn-upgrade

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

1 similar comment
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

@openshift-ci OpenShift CI
Copy link
Contributor

openshift-ci bot commented Jan 14, 2025 •
edited
Loading

@jcaamano: 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/4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade 69a1624 link false /test 4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
ci/prow/okd-scos-e2e-aws-ovn 69a1624 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-hypershift-ovn-kubevirt 69a1624 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 69a1624 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/security 69a1624 link false /test security

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.

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

@tssurya
Copy link
Contributor

tssurya commented Jan 15, 2025

/retest-required

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 2a17ab8 and 2 for PR HEAD 69a1624 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 722d631 and 1 for PR HEAD 69a1624 in total

@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 722d631 and 2 for PR HEAD 69a1624 in total

@openshift-merge-bot openshift-merge-bot bot merged commit 626852b into openshift:master Jan 16, 2025
30 of 35 checks passed
@openshift-cherrypick-robot
Copy link

@tssurya: new pull request created: #2620

In response to this:

/cherry-pick release-4.18

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.

@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Jan 16, 2025
Merged
@openshift-bot
Copy link
Contributor

[ART PR BUILD NOTIFIER]

Distgit: cluster-network-operator
This PR has been included in build cluster-network-operator-container-v4.19.0-202501160706.p0.g626852b.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@dougbtv dougbtv Awaiting requested review from dougbtv

@JacobTanenbaum JacobTanenbaum Awaiting requested review from JacobTanenbaum

Assignees

@npinaeva npinaeva

Labels
acknowledge-critical-fixes-only Indicates if the issuer of the label is OK with the policy. approved Indicates a PR has been approved by an approver from all required OWNERS files. 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
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
6 participants
@jcaamano @npinaeva @tssurya @openshift-ci-robot @openshift-cherrypick-robot @openshift-bot