Skip to content

[release-4.19] CORENET-6148: Promote RouteAdvertisements feature gate to default feature set#2425

Merged
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.19from
arghosh93:lift_ra_FG
Sep 2, 2025
Merged

[release-4.19] CORENET-6148: Promote RouteAdvertisements feature gate to default feature set#2425
openshift-merge-bot[bot] merged 1 commit into
openshift:release-4.19from
arghosh93:lift_ra_FG

Conversation

@arghosh93
Copy link
Copy Markdown
Contributor

@arghosh93 arghosh93 commented Jul 28, 2025

This PR lifts the FG for RouteAdvertisements feature.

RouteAdvertisements feature gate was lifted in 4.20 via below PR:
#2225

Signed-off-by: Arnab Ghosh <arnabghosh89@gmail.com>
@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 28, 2025

@arghosh93: This pull request references CORENET-6148 which is a valid jira issue.

Details

In response to this:

This PR lifts the FG for RouteAdvertisements feature

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-reference Indicates that this PR references a valid Jira ticket of any type. label Jul 28, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 28, 2025

Hello @arghosh93! 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 the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jul 28, 2025
@openshift-ci openshift-ci Bot requested review from JoelSpeed and everettraven July 28, 2025 10:44
@JoelSpeed
Copy link
Copy Markdown
Contributor

@arghosh93 Please link the associated SBAR in the PR description

Also, schema checker is reporting existing issues that cannot be fixed, we can override that

/override ci/prow/verify-crd-schema

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Jul 28, 2025

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

Details

In response to this:

@arghosh93 Please link the associated SBAR in the PR description

Also, schema checker is reporting existing issues that cannot be fixed, we can override that

/override ci/prow/verify-crd-schema

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

tssurya commented Jul 28, 2025

@arghosh93 Please link the associated SBAR in the PR description

Also, schema checker is reporting existing issues that cannot be fixed, we can override that

/override ci/prow/verify-crd-schema

yea will open a SBAR and link it here.

@openshift-ci-robot
Copy link
Copy Markdown

openshift-ci-robot commented Jul 28, 2025

@arghosh93: This pull request references CORENET-6148 which is a valid jira issue.

Details

In response to this:

This PR lifts the FG for RouteAdvertisements feature.

RouteAdvertisements feature gate was lifted in 4.20 via below PR:
#2225

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.

@arghosh93
Copy link
Copy Markdown
Contributor Author

/hold
Till we are working on the SBAR.

@openshift-ci openshift-ci Bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 28, 2025
@sdodson
Copy link
Copy Markdown
Member

sdodson commented Aug 4, 2025

/test verify-feature-promotion

4 similar comments
@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 8, 2025

/test verify-feature-promotion

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 11, 2025

/test verify-feature-promotion

@jcaamano
Copy link
Copy Markdown
Contributor

/test verify-feature-promotion

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 14, 2025

/test verify-feature-promotion

@jcaamano
Copy link
Copy Markdown
Contributor

@JoelSpeed I think these numbers do not add up

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 [Timeout:30m] [Suite:openshift/conformance/parallel]" only has 13 runs, need at least 14 runs 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 External host should be able to query route advertised pods by the pod IP [Suite:openshift/conformance/parallel]" only has 12 runs, need at least 14 runs 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 has 12 runs, need at least 14 runs for "RouteAdvertisements" on {metal amd64 ha dual}

They run daily and they have been running for more than 14 days. What are we missing?

@JoelSpeed
Copy link
Copy Markdown
Contributor

If for any reason the cluster failed to come up one or two of those days, you'll have missed out on the data as the result wouldn't be recorded for a cluster bootstrapping fail.

The best thing to do here would be to work out which job you need to run to trigger those tests and use gangway-cli to trigger say 5 more runs

@jcaamano
Copy link
Copy Markdown
Contributor

If for any reason the cluster failed to come up one or two of those days, you'll have missed out on the data as the result wouldn't be recorded for a cluster bootstrapping fail.

The best thing to do here would be to work out which job you need to run to trigger those tests and use gangway-cli to trigger say 5 more runs

It's strange though that it just happens to those particular test cases if entire jobs failed to run. Will run gangway as you suggested, thanks.

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 18, 2025

/test verify-feature-promotion

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 19, 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 IPv4 [Suite:openshift/conformance/parallel]" only passed 94%, need at least 95% for "RouteAdvertisements" on {metal amd64 ha dual}

@jcaamano we are almost there.

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 19, 2025

/test verify-feature-promotion

1 similar comment
@jcaamano
Copy link
Copy Markdown
Contributor

/test verify-feature-promotion

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 20, 2025

The verify lane is looking much better. The tests are at the correct pass rate above 95% on the dualstack lanes we have.

error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {metal amd64 ha ipv4}
error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {metal amd64 ha ipv6}
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 }
F0820 08:20:22.479751   10369 root.go:64] Error running codegen: error: only 0 tests found, need at least 5 for "RouteAdvertisements" on {vsphere amd64 ha }

It's failing for platform reasons. Is this something you can override @JoelSpeed or do we need to do anything on our side.

As for the SBAR: I had opened it 20 days ago: https://docs.google.com/presentation/d/1Ak0bkXFkvoY8JxipMQGct8uCWroPNc84V64PjmXFyek/edit?slide=id.g9814768380_0_0#slide=id.g9814768380_0_0 haven't heard back though @davegord is helping me get some eyes on this.

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Aug 20, 2025

/hold

please don't remove hold (@jcaamano will do it once we are ready on ovnk/cno side fully) we are only trying to ensure we get this PR to a ready state in parallel.

@arghosh93
Copy link
Copy Markdown
Contributor Author

/test verify-feature-promotion

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Sep 1, 2025

@JoelSpeed : PTAL, we are trying to graduate this feature some time this week. All development PRs have been backported into 4.19 already. I have gotten OCP leadership ACK on SBAR, we are waiting on the BU ack still which I will let you know as soon as we hear back.

@JoelSpeed
Copy link
Copy Markdown
Contributor

Changes LGTM, ping when you have the BU ack and I'll get it tagged

@JoelSpeed
Copy link
Copy Markdown
Contributor

SBAR now has the appropriate approvals

/lgtm
/override ci/prow/verify-feature-promotion
/label backport-risk-assessed
/label jira/valid-bug

@openshift-ci openshift-ci Bot added backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. labels Sep 2, 2025
@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label Sep 2, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: arghosh93, 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 Sep 2, 2025
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 2, 2025

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

Details

In response to this:

SBAR now has the appropriate approvals

/lgtm
/override ci/prow/verify-feature-promotion
/label backport-risk-assessed
/label jira/valid-bug

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

/verified by ci/prow/verify-feature-promotion

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Sep 2, 2025
@openshift-ci-robot
Copy link
Copy Markdown

@JoelSpeed: This PR has been marked as verified by [ci/prow/verify-feature-promotion](https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/openshift_api/2425/pull-ci-openshift-api-release-4.19-verify-feature-promotion/1960195290258477056).

Details

In response to this:

/verified by 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 openshift-eng/jira-lifecycle-plugin repository.

@JoelSpeed
Copy link
Copy Markdown
Contributor

/hold cancel

SBAR has been approved

@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 Sep 2, 2025
@openshift-ci-robot
Copy link
Copy Markdown

/retest-required

Remaining retests: 0 against base HEAD 1c614f5 and 2 for PR HEAD d68a59c in total

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

/retest-required

Remaining retests: 0 against base HEAD 1c614f5 and 2 for PR HEAD d68a59c in total

@arghosh93
Copy link
Copy Markdown
Contributor Author

/retest-required

@tssurya
Copy link
Copy Markdown
Contributor

tssurya commented Sep 2, 2025

/test verify-crd-schema

hmm this seems red for reasons not related to this PR? is this something we need to fix as FUP? @JoelSpeed ?

----- SCHEMACHECK -----
ERROR: ConditionsMustHaveProperSSATags: crd/networks.operator.openshift.io version/v1 field/^.status.condition must define valid condition properties: observedGeneration attribute is missing
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.useMultiNetworkPolicy may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.migration.features.egressFirewall may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.migration.features.egressIP may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.migration.features.multicast may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.defaultNetwork.openshiftSDNConfig.useExternalOpenvswitch may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.defaultNetwork.openshiftSDNConfig.enableUnidling may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.defaultNetwork.ovnKubernetesConfig.gatewayConfig.routingViaHost may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.deployKubeProxy may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.disableNetworkDiagnostics may not be a boolean
ERROR: NoBools: crd/networks.operator.openshift.io version/v1 field/^.spec.disableMultiNetwork may not be a boolean
ERROR: NoMaps: crd/networks.operator.openshift.io version/v1 field/^.spec.kubeProxyConfig.proxyArguments may not be a map

maybe we need a bug for this?

@everettraven
Copy link
Copy Markdown
Contributor

@tssurya I saw that Joel overrode the verify-crd-schema check previously: #2425 (comment)

Overriding for same reasons.

/override ci/prow/verify-crd-schema

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 2, 2025

@everettraven: everettraven unauthorized: /override is restricted to Repo administrators, approvers in top level OWNERS file, and the following github teams:openshift: openshift-release-oversight openshift-staff-engineers openshift-sustaining-engineers.

Details

In response to this:

@tssurya I saw that Joel overrode the verify-crd-schema check previously: #2425 (comment)

Overriding for same reasons.

/override ci/prow/verify-crd-schema

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.

@knobunc
Copy link
Copy Markdown
Contributor

knobunc commented Sep 2, 2025

/override ci/prow/verify-crd-schema

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented Sep 2, 2025

@knobunc: Overrode contexts on behalf of knobunc: ci/prow/verify-crd-schema

Details

In response to this:

/override ci/prow/verify-crd-schema

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 Sep 2, 2025

@arghosh93: 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/okd-scos-e2e-aws-ovn d68a59c link false /test okd-scos-e2e-aws-ovn
ci/prow/verify-crd-schema d68a59c link true /test verify-crd-schema

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-merge-bot openshift-merge-bot Bot merged commit c9f500d into openshift:release-4.19 Sep 2, 2025
24 of 25 checks passed
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. 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. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.