Skip to content

Promote RouteAdvertisements feature gate to default feature set#2225

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
jcaamano:lift-fg-ra
Jun 5, 2025
Merged

Promote RouteAdvertisements feature gate to default feature set#2225
openshift-merge-bot[bot] merged 1 commit into
openshift:masterfrom
jcaamano:lift-fg-ra

Conversation

@jcaamano
Copy link
Copy Markdown
Contributor

No description provided.

@jcaamano
Copy link
Copy Markdown
Contributor Author

/hold

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 11, 2025

Hello @jcaamano! Some important instructions when contributing to openshift/api:
API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.

@openshift-ci openshift-ci Bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Mar 11, 2025
@openshift-ci openshift-ci Bot requested review from JoelSpeed and deads2k March 11, 2025 19:41
@JoelSpeed
Copy link
Copy Markdown
Contributor

/retitle Promote RouteAdvertisements feature gate to default feature set

Retitling for consistency/searchability in the future

@openshift-ci openshift-ci Bot changed the title Lift 4.19 feature gate for RouteAdvertisements Promote RouteAdvertisements feature gate to default feature set Mar 12, 2025
@jcaamano
Copy link
Copy Markdown
Contributor Author

/test ?

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Mar 12, 2025

@jcaamano: The following commands are available to trigger required jobs:

/test build
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial
/test e2e-aws-serial-techpreview
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test images
/test integration
/test lint
/test minor-e2e-upgrade-minor
/test minor-images
/test unit
/test verify
/test verify-client-go
/test verify-crd-schema
/test verify-deps
/test verify-feature-promotion

The following commands are available to trigger optional jobs:

/test e2e-azure
/test e2e-gcp
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

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

pull-ci-openshift-api-master-build
pull-ci-openshift-api-master-e2e-aws-ovn
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift
pull-ci-openshift-api-master-e2e-aws-ovn-techpreview
pull-ci-openshift-api-master-e2e-aws-serial
pull-ci-openshift-api-master-e2e-aws-serial-techpreview
pull-ci-openshift-api-master-e2e-azure
pull-ci-openshift-api-master-e2e-gcp
pull-ci-openshift-api-master-e2e-upgrade
pull-ci-openshift-api-master-e2e-upgrade-out-of-change
pull-ci-openshift-api-master-images
pull-ci-openshift-api-master-integration
pull-ci-openshift-api-master-lint
pull-ci-openshift-api-master-minor-e2e-upgrade-minor
pull-ci-openshift-api-master-minor-images
pull-ci-openshift-api-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-api-master-unit
pull-ci-openshift-api-master-verify
pull-ci-openshift-api-master-verify-client-go
pull-ci-openshift-api-master-verify-crd-schema
pull-ci-openshift-api-master-verify-deps
pull-ci-openshift-api-master-verify-feature-promotion
Details

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.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 15, 2025
@maiqueb
Copy link
Copy Markdown
Contributor

maiqueb commented May 21, 2025

/cc

@openshift-ci openshift-ci Bot requested a review from maiqueb May 21, 2025 10:57
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 26, 2025
@jcaamano
Copy link
Copy Markdown
Contributor Author

error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {aws amd64 ha }
error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {azure amd64 ha }
error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {gcp amd64 ha }
error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {vsphere amd64 ha }

This feature only targets metal

@jcaamano
Copy link
Copy Markdown
Contributor Author

jcaamano commented May 26, 2025

error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For cluster user defined networks When the network topology is Layer 3 UDN pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv4 [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For cluster user defined networks When the network topology is Layer 3 UDN pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv4 [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv4 [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv4 [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 3 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 3 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For cluster user defined networks When the network topology is Layer 3 UDN pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For cluster user defined networks When the network topology is Layer 3 UDN pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd[64](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2225/pull-ci-openshift-api-master-verify-feature-promotion/1926984361840742400#1:build-log.txt%3A64) ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 External host should be able to query route advertised pods by the pod IP [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 External host should be able to query route advertised pods by the pod IP [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 3 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 3 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] External host should be able to query route advertised pods by the pod IP [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] External host should be able to query route advertised pods by the pod IP [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only has 1 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha ipv6}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising the default network [apigroup:user.openshift.io][apigroup:security.openshift.io] Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 0%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha ipv6}

It seems like the tooling is picking up results from jobs that should not be running these tests. The problem is that the test itself fails for unrelated reason before it has the chance to check if it should be skipped or not. Discussed on slack
https://redhat-internal.slack.com/archives/C01CQA76KMX/p1747652922183309?thread_ts=1747390032.669289&cid=C01CQA76KMX
Seems to be a tooling pitfall.

@jcaamano
Copy link
Copy Markdown
Contributor Author

jcaamano commented May 26, 2025

error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]" only passed 91%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha dual}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]" only passed 78%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha dual}
error: "[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]" only passed 86%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha dual}

Most of the flakes are due to reasons unrelated to the feature:

[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over a VRF-Lite configuration Pods should be able to communicate on a secondary network [Suite:openshift/conformance/parallel]

has flaked three times
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1926488619011280896
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1925401449680867328
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1925039125904232448

All of them are due to https://issues.redhat.com/browse/OCPBUGS-56488, unrelated to this feature.
There is a bug on a knmstate liveness probe, that makes any of their pods restart. This has two consequences that can be observed:

  • A delay when applying a CRD instance that might cause a timeout on the test.
  • When one of those pods restart, they rollback network configuration performed by this, or other tests, making them fail.

Unlikely to get 95% pass rate until the root cause is fixed.


[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [PodNetwork] Advertising a cluster user defined network [apigroup:user.openshift.io][apigroup:security.openshift.io] Over the default VRF When the network topology is Layer 2 Pods should communicate with external host without being SNATed [Suite:openshift/conformance/parallel]

flaked once
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-techpreview/1924812607089283072
being one of the other tests impacted by the previous problem.

failed once
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-techpreview/1924812622679511040
along with many other tests because one node became not ready. We looked but we haven't been able to trace the reason why this happened, nor been able to establish any relation to the feature itself.


[sig-network][OCPFeatureGate:RouteAdvertisements][Feature:RouteAdvertisements][apigroup:operator.openshift.io] when using openshift ovn-kubernetes [EgressIP] Advertising EgressIP [apigroup:user.openshift.io][apigroup:security.openshift.io] For the default network Pods should have the assigned EgressIPs and EgressIPs can be created, updated and deleted [apigroup:route.openshift.io] When the network is IPv6 [Suite:openshift/conformance/parallel]

flaked 4 times.
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-techpreview/1923589508767420416
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1923951899648724992
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-local-gw-techpreview/1925039125904232448
https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-dualstack-bgp-techpreview/1925401452163895296

3 of those were due to what was fixed with openshift/origin#29803 however the fix did only take effect recently because no CI builds were being accepted for most of last week

The other one is also due to OCPBUGS-56488.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/test ci/prow/verify-feature-promotion

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 27, 2025

@JoelSpeed: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test build
/test e2e-aws-ovn
/test e2e-aws-ovn-hypershift
/test e2e-aws-ovn-hypershift-conformance
/test e2e-aws-ovn-techpreview
/test e2e-aws-serial-1of2
/test e2e-aws-serial-2of2
/test e2e-aws-serial-techpreview-1of2
/test e2e-aws-serial-techpreview-2of2
/test e2e-upgrade
/test e2e-upgrade-out-of-change
/test images
/test integration
/test lint
/test minor-e2e-upgrade-minor
/test minor-images
/test unit
/test verify
/test verify-client-go
/test verify-crd-schema
/test verify-deps
/test verify-feature-promotion

The following commands are available to trigger optional jobs:

/test e2e-azure
/test e2e-gcp
/test okd-scos-e2e-aws-ovn
/test okd-scos-images

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

pull-ci-openshift-api-master-build
pull-ci-openshift-api-master-e2e-aws-ovn
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift
pull-ci-openshift-api-master-e2e-aws-ovn-hypershift-conformance
pull-ci-openshift-api-master-e2e-aws-ovn-techpreview
pull-ci-openshift-api-master-e2e-aws-serial-1of2
pull-ci-openshift-api-master-e2e-aws-serial-2of2
pull-ci-openshift-api-master-e2e-aws-serial-techpreview-1of2
pull-ci-openshift-api-master-e2e-aws-serial-techpreview-2of2
pull-ci-openshift-api-master-e2e-azure
pull-ci-openshift-api-master-e2e-gcp
pull-ci-openshift-api-master-e2e-upgrade
pull-ci-openshift-api-master-e2e-upgrade-out-of-change
pull-ci-openshift-api-master-images
pull-ci-openshift-api-master-integration
pull-ci-openshift-api-master-lint
pull-ci-openshift-api-master-minor-e2e-upgrade-minor
pull-ci-openshift-api-master-minor-images
pull-ci-openshift-api-master-okd-scos-e2e-aws-ovn
pull-ci-openshift-api-master-unit
pull-ci-openshift-api-master-verify
pull-ci-openshift-api-master-verify-client-go
pull-ci-openshift-api-master-verify-crd-schema
pull-ci-openshift-api-master-verify-deps
pull-ci-openshift-api-master-verify-feature-promotion
Details

In response to this:

/test ci/prow/verify-feature-promotion

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.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/test verify-feature-promotion

1 similar comment
@JoelSpeed
Copy link
Copy Markdown
Contributor

/test verify-feature-promotion

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 30, 2025
Signed-off-by: Jaime Caamaño Ruiz <jcaamano@redhat.com>
@openshift-merge-robot openshift-merge-robot removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label May 30, 2025
@JoelSpeed
Copy link
Copy Markdown
Contributor

/test verify-feature-promotion

@jcaamano
Copy link
Copy Markdown
Contributor Author

jcaamano commented Jun 4, 2025

/retest

@JoelSpeed
Copy link
Copy Markdown
Contributor

/override ci/prow/verify-crd-schema

Existing issues that cannot be resolved now

/override ci/prow/verify-feature-promotion

This feature is only applicable to the metal platform and is only being tested on dual stack due to limitations in CI capacity (though there are single stack specific tests).

Per the latest results only a single test is showing below 95%, however, this test was renamed and the new name shows at least 95% over the last 7 days.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Jun 4, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 4, 2025

[APPROVALNOTIFIER] This PR is APPROVED

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

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 Jun 4, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 4, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema, ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/verify-crd-schema

Existing issues that cannot be resolved now

/override ci/prow/verify-feature-promotion

This feature is only applicable to the metal platform and is only being tested on dual stack due to limitations in CI capacity (though there are single stack specific tests).

Per the latest results only a single test is showing below 95%, however, this test was renamed and the new name shows at least 95% over the last 7 days.

/lgtm

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.

@jcaamano
Copy link
Copy Markdown
Contributor Author

jcaamano commented Jun 4, 2025

/hold

Waiting for a couple of hours to sync with the whole team

@jcaamano
Copy link
Copy Markdown
Contributor Author

jcaamano commented Jun 5, 2025

/hold cancel

@openshift-ci openshift-ci Bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jun 5, 2025
@JoelSpeed
Copy link
Copy Markdown
Contributor

/override ci/prow/verify-crd-schema

Existing issues that cannot be resolved now

/override ci/prow/verify-feature-promotion

This feature is only applicable to the metal platform and is only being tested on dual stack due to limitations in CI capacity (though there are single stack specific tests).

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jun 5, 2025

@JoelSpeed: Overrode contexts on behalf of JoelSpeed: ci/prow/verify-crd-schema, ci/prow/verify-feature-promotion

Details

In response to this:

/override ci/prow/verify-crd-schema

Existing issues that cannot be resolved now

/override ci/prow/verify-feature-promotion

This feature is only applicable to the metal platform and is only being tested on dual stack due to limitations in CI capacity (though there are single stack specific tests).

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

openshift-ci Bot commented Jun 5, 2025

@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/e2e-aws-serial-techpreview 2197413 link true /test e2e-aws-serial-techpreview
ci/prow/e2e-aws-serial 2197413 link true /test e2e-aws-serial
ci/prow/okd-scos-e2e-aws-ovn 6ff8c5b link false /test okd-scos-e2e-aws-ovn

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-sigs/prow repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD a0fb5f4 and 2 for PR HEAD 6ff8c5b in total

@openshift-merge-bot openshift-merge-bot Bot merged commit 017e9dd into openshift:master Jun 5, 2025
25 of 26 checks passed
@openshift-bot
Copy link
Copy Markdown

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-config-api
This PR has been included in build ose-cluster-config-api-container-v4.20.0-202506060110.p0.g017e9dd.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. lgtm Indicates that a PR is ready to be merged. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants