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

SDN-5085: Add support for route advertisements #2442

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jcaamano
Copy link
Contributor

No description provided.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 19, 2024
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Jul 19, 2024

@jcaamano: This pull request references SDN-5085 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 story to target the "4.17.0" version, but no target version was set.

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.

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Jul 19, 2024
Copy link
Contributor

openshift-ci bot commented Jul 19, 2024

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

Copy link
Contributor

openshift-ci bot commented Jul 19, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 19, 2024
@jcaamano
Copy link
Contributor Author

/test e2e-gcp-ovn

@jcaamano jcaamano changed the title SDN-5085: Add route advertisements flag handling SDN-5085: Add support for route advertisements Jul 19, 2024
@jcaamano jcaamano force-pushed the routeadvertisements branch 4 times, most recently from f0f1d1e to 05d670e Compare July 19, 2024 18:52
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 24, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Jul 26, 2024
@jcaamano jcaamano marked this pull request as ready for review August 8, 2024 10:20
@openshift-ci openshift-ci bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 8, 2024
@openshift-ci openshift-ci bot requested review from abhat and tssurya August 8, 2024 10:21
@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Aug 8, 2024
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 2, 2024
Signed-off-by: Jaime Caamaño Ruiz <[email protected]>
Copy link
Contributor

openshift-ci bot commented Sep 2, 2024

@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.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade 5944186 link false /test 4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade
ci/prow/e2e-ovn-hybrid-step-registry 2550f00 link false /test e2e-ovn-hybrid-step-registry
ci/prow/4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade 2550f00 link false /test 4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
ci/prow/e2e-aws-hypershift-ovn-kubevirt 2550f00 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade 2550f00 link false /test 4.18-upgrade-from-stable-4.17-e2e-aws-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 2550f00 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-vsphere-ovn-dualstack 2550f00 link false /test e2e-vsphere-ovn-dualstack
ci/prow/e2e-ovn-ipsec-step-registry 2550f00 link false /test e2e-ovn-ipsec-step-registry
ci/prow/e2e-azure-ovn 2550f00 link false /test e2e-azure-ovn
ci/prow/e2e-aws-ovn-windows 2550f00 link true /test e2e-aws-ovn-windows
ci/prow/e2e-aws-ovn-hypershift-conformance 2550f00 link true /test e2e-aws-ovn-hypershift-conformance
ci/prow/security 2550f00 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.

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. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants