Skip to content
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

All 1.7 e2e tests are broken #2273

Closed
tuminoid opened this issue Jan 24, 2025 · 2 comments
Closed

All 1.7 e2e tests are broken #2273

tuminoid opened this issue Jan 24, 2025 · 2 comments
Assignees
Labels
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. triage/accepted Indicates an issue is ready to be actively worked on.

Comments

@tuminoid
Copy link
Member

Which jobs are failing?

CAPM3 e2e 1.7 branch jobs (which are not maintained, but are CI tested, so CI should stay green) are failing.

Which tests are failing?

All. e2e integration, features, pivoting, remediation etc.

[2025-01-23T20:19:53.629Z]   [FAILED] Timed out after 1800.001s.
[2025-01-23T20:19:53.629Z]   No Control Plane machines came into existence. 

Since when has it been failing?

Since we merged dev-env UEFI support. on Jan 20th.

Jenkins link

https://jenkins.nordix.org/blue/organizations/jenkins/metal3-periodic-centos-e2e-feature-test-release-1-7-pivoting/detail/metal3-periodic-centos-e2e-feature-test-release-1-7-pivoting/103/pipeline

Reason for failure (if possible)

Assumption is that node images for v1.29 are not UEFI compatible and need to be rebuilt.

Anything else we need to know?

Live-iso failure in 1.7 is not related, it has separate fix here. It occurs before CP issue can, so the 1.7 e2e feature will fail to CP issue when live-iso issue is fixed. Unfortunately that cannot be merged as any e2e verification job fails to CP issue.

Label(s) to be applied

/kind failing-test
/triage accepted
/assign @Sunnatillo

@metal3-io-bot metal3-io-bot added kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. triage/accepted Indicates an issue is ready to be actively worked on. labels Jan 24, 2025
@tuminoid
Copy link
Member Author

tuminoid commented Feb 3, 2025

Issue has been fixed. It required various old k8s images built by 1.7 to be rebuilt with UEFI support. No linked PRs, images updated in ARM.

/close

@metal3-io-bot
Copy link
Contributor

@tuminoid: Closing this issue.

In response to this:

Issue has been fixed. It required various old k8s images built by 1.7 to be rebuilt with UEFI support. No linked PRs, images updated in ARM.

/close

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
kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. triage/accepted Indicates an issue is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants