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

Investigate failing KinD tests #7701

Open
Cali0707 opened this issue Feb 16, 2024 · 1 comment · May be fixed by #7784
Open

Investigate failing KinD tests #7701

Cali0707 opened this issue Feb 16, 2024 · 1 comment · May be fixed by #7784
Assignees
Labels
area/test-and-release Test infrastructure, tests or release kind/bug Categorizes issue or PR as related to a bug. triage/accepted Issues which should be fixed (post-triage)

Comments

@Cali0707
Copy link
Member

Describe the bug
Currently, KinD tests are often failing with error logs like:

"status": {
                        "phase": "Pending",
                        "conditions": [
                          {
                            "type": "PodScheduled",
                            "status": "False",
                            "lastProbeTime": null,
                            "lastTransitionTime": "2024-02-16T20:53:17Z",
                            "reason": "Unschedulable",
                            "message": "0/2 nodes are available: 1 Too many pods, 1 node(s) had untolerated taint {node-role.kubernetes.io/control-plane: }. preemption: 0/2 nodes are available: 1 No preemption victims found for incoming pod, 1 Preemption is not helpful for scheduling.."
                          }
                        ],
                        "qosClass": "BestEffort"

Expected behavior
KinD tests pass

To Reproduce
Look at most PRs, KinD tests have failed

Knative release version
main

Additional context
Add any other context about the problem here such as proposed priority

@Cali0707 Cali0707 added kind/bug Categorizes issue or PR as related to a bug. area/test-and-release Test infrastructure, tests or release labels Feb 16, 2024
@Cali0707
Copy link
Member Author

From WG discussion today: to fix, lets run a subset of tests

@pierDipi pierDipi added the triage/accepted Issues which should be fixed (post-triage) label Feb 22, 2024
@Cali0707 Cali0707 self-assigned this Mar 12, 2024
@Cali0707 Cali0707 linked a pull request Mar 12, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/test-and-release Test infrastructure, tests or release kind/bug Categorizes issue or PR as related to a bug. triage/accepted Issues which should be fixed (post-triage)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants