Skip to content

Conversation

@mtulio
Copy link
Contributor

@mtulio mtulio commented Mar 24, 2025

This change register the platform type external as a valid provider (flag) when running the conformance tests.

This is required if we need more refinement when running conformance tests in that platform type (External), which was design inheriting from None. EP for more information: https://github.com/openshift/enhancements/blob/master/enhancements/cloud-integration/infrastructure-external-platform-type.md

For more information about the tests executed in this PR, see this comment: #29623 (comment)

[1] OCPBUGS-53249 - The following PR implements granular skips for platform specific on tests coming from kubernetes suites: openshift/kubernetes#2247

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

@mtulio: This pull request references Jira Issue OCPBUGS-53249, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.19.0) matches configured target version for branch (4.19.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

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

Details

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

openshift-ci bot commented Mar 24, 2025

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

@mtulio
Copy link
Contributor Author

mtulio commented Mar 24, 2025

/test ?

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Mar 24, 2025

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

/test e2e-aws-jenkins
/test e2e-aws-ovn-edge-zones
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-image-registry
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial
/test e2e-gcp-ovn
/test e2e-gcp-ovn-builds
/test e2e-gcp-ovn-image-ecosystem
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi
/test images
/test lint
/test okd-scos-images
/test unit
/test verify
/test verify-deps

The following commands are available to trigger optional jobs:

/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
/test e2e-agnostic-ovn-cmd
/test e2e-aws
/test e2e-aws-csi
/test e2e-aws-disruptive
/test e2e-aws-etcd-certrotation
/test e2e-aws-etcd-recovery
/test e2e-aws-ovn
/test e2e-aws-ovn-cgroupsv2
/test e2e-aws-ovn-etcd-scaling
/test e2e-aws-ovn-ipsec-serial
/test e2e-aws-ovn-kube-apiserver-rollout
/test e2e-aws-ovn-kubevirt
/test e2e-aws-ovn-single-node
/test e2e-aws-ovn-single-node-serial
/test e2e-aws-ovn-single-node-techpreview
/test e2e-aws-ovn-single-node-techpreview-serial
/test e2e-aws-ovn-single-node-upgrade
/test e2e-aws-ovn-upgrade
/test e2e-aws-ovn-upgrade-rollback
/test e2e-aws-ovn-upi
/test e2e-aws-ovn-virt-techpreview
/test e2e-aws-proxy
/test e2e-azure
/test e2e-azure-ovn-etcd-scaling
/test e2e-azure-ovn-upgrade
/test e2e-baremetalds-kubevirt
/test e2e-external-aws
/test e2e-external-aws-ccm
/test e2e-external-vsphere-ccm
/test e2e-gcp-csi
/test e2e-gcp-disruptive
/test e2e-gcp-fips-serial
/test e2e-gcp-ovn-etcd-scaling
/test e2e-gcp-ovn-rt-upgrade
/test e2e-gcp-ovn-techpreview
/test e2e-gcp-ovn-techpreview-serial
/test e2e-hypershift-conformance
/test e2e-metal-ipi-ovn
/test e2e-metal-ipi-ovn-dualstack
/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
/test e2e-metal-ipi-ovn-dualstack-local-gateway
/test e2e-metal-ipi-ovn-kube-apiserver-rollout
/test e2e-metal-ipi-serial
/test e2e-metal-ipi-serial-ovn-ipv6
/test e2e-metal-ipi-virtualmedia
/test e2e-metal-ovn-single-node-live-iso
/test e2e-metal-ovn-single-node-with-worker-live-iso
/test e2e-openstack-ovn
/test e2e-openstack-serial
/test e2e-vsphere-ovn-dualstack-primaryv6
/test e2e-vsphere-ovn-etcd-scaling
/test okd-e2e-gcp
/test okd-scos-e2e-aws-ovn

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

pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
pull-ci-openshift-origin-main-e2e-agnostic-ovn-cmd
pull-ci-openshift-origin-main-e2e-aws
pull-ci-openshift-origin-main-e2e-aws-csi
pull-ci-openshift-origin-main-e2e-aws-disruptive
pull-ci-openshift-origin-main-e2e-aws-ovn
pull-ci-openshift-origin-main-e2e-aws-ovn-cgroupsv2
pull-ci-openshift-origin-main-e2e-aws-ovn-edge-zones
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-aws-ovn-fips
pull-ci-openshift-origin-main-e2e-aws-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift
pull-ci-openshift-origin-main-e2e-aws-ovn-microshift-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-serial
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-upgrade
pull-ci-openshift-origin-main-e2e-aws-ovn-upgrade
pull-ci-openshift-origin-main-e2e-aws-proxy
pull-ci-openshift-origin-main-e2e-azure
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-azure-ovn-upgrade
pull-ci-openshift-origin-main-e2e-gcp-csi
pull-ci-openshift-origin-main-e2e-gcp-disruptive
pull-ci-openshift-origin-main-e2e-gcp-fips-serial
pull-ci-openshift-origin-main-e2e-gcp-ovn
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-gcp-ovn-rt-upgrade
pull-ci-openshift-origin-main-e2e-gcp-ovn-upgrade
pull-ci-openshift-origin-main-e2e-hypershift-conformance
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-bgp-techpreview
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-local-gateway
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout
pull-ci-openshift-origin-main-e2e-metal-ipi-serial
pull-ci-openshift-origin-main-e2e-metal-ipi-serial-ovn-ipv6
pull-ci-openshift-origin-main-e2e-metal-ipi-virtualmedia
pull-ci-openshift-origin-main-e2e-openstack-ovn
pull-ci-openshift-origin-main-e2e-openstack-serial
pull-ci-openshift-origin-main-e2e-vsphere-ovn
pull-ci-openshift-origin-main-e2e-vsphere-ovn-dualstack-primaryv6
pull-ci-openshift-origin-main-e2e-vsphere-ovn-etcd-scaling
pull-ci-openshift-origin-main-e2e-vsphere-ovn-upi
pull-ci-openshift-origin-main-images
pull-ci-openshift-origin-main-lint
pull-ci-openshift-origin-main-okd-e2e-gcp
pull-ci-openshift-origin-main-okd-scos-e2e-aws-ovn
pull-ci-openshift-origin-main-okd-scos-images
pull-ci-openshift-origin-main-unit
pull-ci-openshift-origin-main-verify
pull-ci-openshift-origin-main-verify-deps
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.

@mtulio
Copy link
Contributor Author

mtulio commented Mar 24, 2025

/test e2e-external-aws-ccm

@stbenjam
Copy link
Member

stbenjam commented Apr 1, 2025

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 1, 2025
@stbenjam
Copy link
Member

stbenjam commented Apr 1, 2025

/lgtm

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 1, 2025
@mtulio
Copy link
Contributor Author

mtulio commented Apr 1, 2025

Adding explicitly the hold label as we are waiting for the presubmit job updates[1] to test here. We wont expect the job to pass, but we should have at least the same result when not setting --provider flag. Final fixes must be addressed in[2] which is blocked by this change.

/hold

[1] openshift/release#63367
[2] openshift/kubernetes#2247

@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 Apr 1, 2025
@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

openshift/release#63367 merged. Testing again:

/test e2e-external-aws-ccm

@openshift-trt
Copy link

openshift-trt bot commented Apr 2, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 2eca6b8

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-external-aws-ccm High - "Find the input image ocp-4.15-upi-installer and tag it into the pipeline" is a new test that was not present in all runs against the current commit.

New tests seen in this PR at sha: 2eca6b8

  • "Find the input image ocp-4.15-upi-installer and tag it into the pipeline" [Total: 2, Pass: 2, Fail: 0, Flake: 0]

@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2025
@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

Fixed the pkg call to register the external provider, got success testing locally, re-testing:

/test e2e-external-aws-ccm

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

Okay, e2e-external presubmit job ran and we are where we wanted:

  • e2e executed with provider flag set to "external"
  • suite executed the same amount of jobs when not setting the provider flag
  • now we are supporting platform type external in the test framework to implement specific log for this kind of integration
  • failed tests is expected: only 2 failures which will be addressed by OCPBUGS-53249: skip UDP LoadBalancer on external  kubernetes#2247

This PR is ready for review.

/unhold
/assign @bertinatto @stbenjam

[1] job result before provider flag: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29623/pull-ci-openshift-origin-main-e2e-external-aws-ccm/1904250996830244864
[2] job result with provider flag: https://prow.ci.openshift.org/view/gs/test-platform-results/pr-logs/pull/29623/pull-ci-openshift-origin-main-e2e-external-aws-ccm/1907368045882380288

@mtulio mtulio marked this pull request as ready for review April 2, 2025 13:45
@openshift-ci openshift-ci bot removed do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. labels Apr 2, 2025
@openshift-ci openshift-ci bot requested review from deads2k and sjenning April 2, 2025 13:51
@vr4manta
Copy link
Contributor

vr4manta commented Apr 2, 2025

/hold
/lgtm

Holding for now till tests are done just to make sure we are happy.

@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 Apr 2, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 2, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 2, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mtulio, stbenjam, vr4manta

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

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

/test images
/test e2e-aws

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

Looking the failures, there are massive image build issues across many jobs. I will wait for stable Ci to triggering tests

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

I am seeing AWS advanced from previous failed steps, calling more common jobs to get readiness:
/test e2e-vsphere-ovn
/test e2e-azure

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

re-calling required failed in the image issues:
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial

@mtulio
Copy link
Contributor Author

mtulio commented Apr 2, 2025

failures>

  • vsphere failed in build image phase (unrelated)
  • e2e-azure failing for the same reason of later
  • e2e-aws is passing
  • e2e-gcp is passing

the last two are touching where we are changing, and the required job for platform external is passing to the point we wanted (blocked by two test failures we are trying to skip in openshift/kubernetes#2247 ).

Even with a lot of CI flakes, I get confidence with finished jobs. I am unblock to keep working on openshift/kubernetes#2247.

/hold cancel
/retest-required

@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 Apr 2, 2025
@openshift-trt
Copy link

openshift-trt bot commented Apr 2, 2025

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New Test Risks for sha: 7aacc91

Job Name New Test Risk
pull-ci-openshift-origin-main-e2e-external-aws-ccm Medium - "Find the input image ocp-4.15-upi-installer and tag it into the pipeline" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 7aacc91

  • "Find the input image ocp-4.15-upi-installer and tag it into the pipeline" [Total: 1, Pass: 1, Fail: 0, Flake: 0]

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD f8b7258 and 2 for PR HEAD 7aacc91 in total

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Apr 3, 2025

@mtulio: 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-azure-ovn-upgrade 7aacc91 link false /test e2e-azure-ovn-upgrade
ci/prow/e2e-agnostic-ovn-cmd 7aacc91 link false /test e2e-agnostic-ovn-cmd
ci/prow/okd-e2e-gcp 7aacc91 link false /test okd-e2e-gcp
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 7aacc91 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview 7aacc91 link false /test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-azure-ovn-etcd-scaling 7aacc91 link false /test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node 7aacc91 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout 7aacc91 link false /test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-openstack-serial 7aacc91 link false /test e2e-openstack-serial
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway 7aacc91 link false /test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-gcp-disruptive 7aacc91 link false /test e2e-gcp-disruptive
ci/prow/e2e-aws-proxy 7aacc91 link false /test e2e-aws-proxy
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback 7aacc91 link false /test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-metal-ipi-serial 7aacc91 link false /test e2e-metal-ipi-serial
ci/prow/e2e-aws-ovn-etcd-scaling 7aacc91 link false /test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-gcp-ovn-rt-upgrade 7aacc91 link false /test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-external-aws-ccm 7aacc91 link false /test e2e-external-aws-ccm
ci/prow/e2e-aws-csi 7aacc91 link false /test e2e-aws-csi
ci/prow/e2e-metal-ipi-ovn 7aacc91 link false /test e2e-metal-ipi-ovn
ci/prow/e2e-aws-ovn 7aacc91 link false /test e2e-aws-ovn
ci/prow/e2e-aws-disruptive 7aacc91 link false /test e2e-aws-disruptive
ci/prow/e2e-aws-ovn-cgroupsv2 7aacc91 link false /test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-aws-ovn-single-node-serial 7aacc91 link false /test e2e-aws-ovn-single-node-serial
ci/prow/e2e-aws-ovn-single-node-upgrade 7aacc91 link false /test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-vsphere-ovn-etcd-scaling 7aacc91 link false /test e2e-vsphere-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-virtualmedia 7aacc91 link false /test e2e-metal-ipi-virtualmedia
ci/prow/e2e-azure 7aacc91 link false /test e2e-azure
ci/prow/e2e-openstack-ovn 7aacc91 link false /test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack 7aacc91 link false /test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-hypershift-conformance 7aacc91 link false /test e2e-hypershift-conformance
ci/prow/e2e-aws-ovn-kube-apiserver-rollout 7aacc91 link false /test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-etcd-scaling 7aacc91 link false /test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-metal-ipi-serial-ovn-ipv6 7aacc91 link false /test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-gcp-fips-serial 7aacc91 link false /test e2e-gcp-fips-serial
ci/prow/e2e-aws-ovn-upgrade 7aacc91 link false /test e2e-aws-ovn-upgrade

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 ea71886 into openshift:main Apr 3, 2025
20 of 55 checks passed
@openshift-ci-robot
Copy link

@mtulio: Jira Issue OCPBUGS-53249: 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-53249 has not been moved to the MODIFIED state.

Details

In response to this:

This change register the platform type external as a valid provider (flag) when running the conformance tests.

This is required if we need more refinement when running conformance tests in that platform type (External), which was design inheriting from None. EP for more information: https://github.com/openshift/enhancements/blob/master/enhancements/cloud-integration/infrastructure-external-platform-type.md

For more information about the tests executed in this PR, see this comment: #29623 (comment)

[1] OCPBUGS-53249 - The following PR implements granular skips for platform specific on tests coming from kubernetes suites: openshift/kubernetes#2247

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: openshift-enterprise-tests
This PR has been included in build openshift-enterprise-tests-container-v4.19.0-202504031145.p0.gea71886.assembly.stream.el9.
All builds following this will include this PR.

@mtulio
Copy link
Contributor Author

mtulio commented Apr 9, 2025

We'll need to backport this to OCP 4.18 as the failed test was introduced in kube 1.31.

/cherry-pick release-4.18

@openshift-cherrypick-robot

@mtulio: new pull request created: #29666

Details

In response to this:

We'll need to backport this to OCP 4.18 as the failed test was introduced in kube 1.31.

/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.

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-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.

7 participants