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.18] OCPBUGS-48710, SDN-4930: Add host isolation mounts to ovnkube-node #2620

Conversation

openshift-cherrypick-robot

This is an automated cherry-pick of #2591

/assign tssurya

@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 16, 2025

@openshift-cherrypick-robot: Ignoring requests to cherry-pick non-bug issues: SDN-4930

In response to this:

This is an automated cherry-pick of #2591

/assign tssurya

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.

Copy link
Contributor

openshift-ci bot commented Jan 16, 2025

@openshift-cherrypick-robot: 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-dualstack-primaryv6 3820221 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/okd-scos-e2e-aws-ovn 3820221 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec 3820221 link false /test e2e-metal-ipi-ovn-ipv6-ipsec
ci/prow/e2e-network-mtu-migration-ovn-ipv6 3820221 link false /test e2e-network-mtu-migration-ovn-ipv6
ci/prow/e2e-aws-hypershift-ovn-kubevirt 3820221 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-azure-ovn 3820221 link false /test e2e-azure-ovn
ci/prow/e2e-ovn-step-registry 3820221 link false /test e2e-ovn-step-registry
ci/prow/security 3820221 link false /test security
ci/prow/e2e-aws-ovn-serial 3820221 link false /test e2e-aws-ovn-serial
ci/prow/e2e-aws-ovn-single-node 3820221 link false /test e2e-aws-ovn-single-node

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.

@kyrtapz
Copy link
Contributor

kyrtapz commented Jan 23, 2025

/lgtm
/label backport-risk-assessed

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Jan 23, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Jan 23, 2025
Copy link
Contributor

openshift-ci bot commented Jan 23, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: kyrtapz, openshift-cherrypick-robot

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 approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 23, 2025
@jechen0648
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 Jan 23, 2025
@kyrtapz
Copy link
Contributor

kyrtapz commented Jan 24, 2025

/retitle [release-4.18] OCPBUGS-48710, SDN-4930: Add host isolation mounts to ovnkube-node

@openshift-ci openshift-ci bot changed the title [release-4.18] SDN-4930: Add host isolation mounts to ovnkube-node [release-4.18] OCPBUGS-48710, SDN-4930: Add host isolation mounts to ovnkube-node Jan 24, 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 24, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jan 24, 2025

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-48710, which is valid.

7 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)
  • release note type set to "Release Note Not Required"
  • dependent bug Jira Issue OCPBUGS-48709 is in the state Verified, which is one of the valid states (MODIFIED, ON_QA, VERIFIED)
  • dependent Jira Issue OCPBUGS-48709 targets the "4.19.0" version, which is one of the valid target versions: 4.19.0
  • bug has dependents

Requesting review from QA contact:
/cc @anuragthehatter

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

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

In response to this:

This is an automated cherry-pick of #2591

/assign tssurya

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.

@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 Jan 24, 2025
@openshift-ci-robot
Copy link
Contributor

/retest-required

Remaining retests: 0 against base HEAD 911d8ef and 2 for PR HEAD 3820221 in total

@openshift-merge-bot openshift-merge-bot bot merged commit a380c49 into openshift:release-4.18 Jan 24, 2025
22 of 32 checks passed
@openshift-ci-robot
Copy link
Contributor

@openshift-cherrypick-robot: Jira Issue OCPBUGS-48710: Some pull requests linked via external trackers have merged:

The following pull requests linked via external trackers have not merged:

These pull request must merge or be unlinked from the Jira bug in order for it to move to the next state. Once unlinked, request a bug refresh with /jira refresh.

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

In response to this:

This is an automated cherry-pick of #2591

/assign tssurya

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.

@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.18.0-202501241602.p0.ga380c49.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
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.