Skip to content

Conversation

@adilGhaffarDev
Copy link
Member

What this PR does / why we need it:
Instead of specifying to upgrade version let capi e2e get the latest available version

Fixes #

Checklist:

  • Documentation has been updated, if necessary.
  • Unit tests have been added, if necessary.
  • E2E tests have been added, if necessary.
  • Integration tests have been added, if necessary.

@adilGhaffarDev
Copy link
Member Author

/test metal3-e2e-clusterctl-upgrade-test-main

@metal3-io-bot metal3-io-bot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 12, 2025
Copy link
Member

@lentzi90 lentzi90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/approve

@metal3-io-bot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lentzi90

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

@metal3-io-bot metal3-io-bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 13, 2025
@adilGhaffarDev
Copy link
Member Author

/test metal3-e2e-clusterctl-upgrade-test-main

@tuminoid
Copy link
Member

/retest

@metal3-io-bot
Copy link
Contributor

metal3-io-bot commented Nov 13, 2025

@adilGhaffarDev: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
metal3-e2e-clusterctl-upgrade-test-main a320b1a link false /test metal3-e2e-clusterctl-upgrade-test-main

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.

@tuminoid
Copy link
Member

[2025-11-13T18:53:19.366Z]   [FAILED] failed to run clusterctl init:
[2025-11-13T18:53:19.366Z]   stdout:
[2025-11-13T18:53:19.366Z]   Fetching providers
[2025-11-13T18:53:19.366Z]   Error: failed to get provider components for the "metal3:v1.11.0" provider: failed to read "components.yaml" from provider's repository "ipam-metal3": failed to read file "/home/metal3ci/tested_repo/_artifacts/repository/ipam-metal3/v1.11.0/components.yaml" from local release v1.11.0: stat /home/metal3ci/tested_repo/_artifacts/repository/ipam-metal3/v1.11.0/components.yaml: no such file or directory

@lentzi90
Copy link
Member

Hmm why is it looking for components.yaml? Shouldn't it be ipam-components.yaml? 🤔

@adilGhaffarDev
Copy link
Member Author

[2025-11-13T18:53:19.366Z]   [FAILED] failed to run clusterctl init:
[2025-11-13T18:53:19.366Z]   stdout:
[2025-11-13T18:53:19.366Z]   Fetching providers
[2025-11-13T18:53:19.366Z]   Error: failed to get provider components for the "metal3:v1.11.0" provider: failed to read "components.yaml" from provider's repository "ipam-metal3": failed to read file "/home/metal3ci/tested_repo/_artifacts/repository/ipam-metal3/v1.11.0/components.yaml" from local release v1.11.0: stat /home/metal3ci/tested_repo/_artifacts/repository/ipam-metal3/v1.11.0/components.yaml: no such file or directory

this version of ipam is missing in e2e config file I will add it there.

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. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants