-
Notifications
You must be signed in to change notification settings - Fork 256
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
🐛 Pinning ironic image release-24.1 where it was missed #1707
🐛 Pinning ironic image release-24.1 where it was missed #1707
Conversation
Signed-off-by: adil ghaffar <muhammad.adil.ghaffar@est.tech>
/cc @dtantsur @elfosardo please check. let me know if I missed anywhere. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/approve |
/test metal3-bmo-e2e-test-pull metal3-centos-e2e-integration-test-release-1-7 |
Needs CI fix in metal3-io/project-infra#732 to merge |
/test metal3-bmo-e2e-test-pull metal3-centos-e2e-integration-test-release-1-7 |
There is something fishy with CI still. Running 1.7 test keyword, it is getting 1.6 CAPM3: [2024-05-06T11:32:48.872Z] /home/metal3ci/metal3/test/e2e/e2e_suite_test.go:102
[2024-05-06T11:32:48.872Z]
[2024-05-06T11:32:48.872Z] [FAILED] Failed to generate the manifest for "infrastructure-metal3" / "v1.6.1" |
I thi
I think CAPM3 1.7 e2e tests wont work properly until metal3-io/cluster-api-provider-metal3#1634 this goes in, correct me @adilGhaffarDev |
it seems like a flake because URL it is complaining about is working fine. https://github.com/metal3-io/cluster-api-provider-metal3/releases/download/v1.6.1/infrastructure-components.yaml lets run it again |
/test metal3-centos-e2e-integration-test-release-1-7 |
point is why should it run that version for a 1.7 test |
yes, we need to merge that PR. regarding failure e2e framework downloads manifests for all the versions that we add in our config( |
ok thats very strange, why should it download the manifest for a version which is not being tested here, is this a CAPI e2e framework feature or I should say limitation ? |
yes, it's part of CAPI e2e framework, we use these manifests in upgrade tests. |
@kashifest can you approve this ? @elfosardo has already approved it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: elfosardo, 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 |
What this PR does / why we need it:
In PR: #1679 ironic image was not pinned everywhere. This PR is fixing it.