-
Notifications
You must be signed in to change notification settings - Fork 72
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
Node drain test not starting due to unable to get chaos resources (ChaosExperiment.litmuschaos.io "node-drain" not found) #2022
Comments
It seems that during this commit, node drain was forgotten. |
In 69dedb3, Litmus version was updated And all links for experiments were changed accordingly except for the node_drain. This commit fixes that. ref: cnti-testcatalog#2022 Signed-off-by: Konstantin Yarovoy <[email protected]>
@kosstennbl @HashNuke @agentpoyo any idea why the issue was not detected in spec tests during github actions? |
@martin-mat please create a new bug issue for the node drain spec test |
Results of running with compiled branch: 14:31:27.784 [pool-73-thread-1] INFO com.matrixx.konstruxx.tools.cnftestsuite.CnfTestsuiteResultParser - Test Score: 100 Score Summary - default Total Essential Tests Passed: 1 Total Bonus Tests Passed: 0 Total Normal Tests Passed: 0 14:31:27.787 [pool-73-thread-1] INFO com.matrixx.konstruxx.Konstruxx - Performing Captures... 14:31:28.050 [pool-73-thread-1] INFO com.matrixx.konstruxx.Konstruxx - Blueprint created |
In 69dedb3, Litmus version was updated And all links for experiments were changed accordingly except for the node_drain. This commit fixes that. ref: #2022 Signed-off-by: Konstantin Yarovoy <[email protected]>
In 69dedb3, Litmus version was updated And all links for experiments were changed accordingly except for the node_drain. This commit fixes that. ref: #2022 Signed-off-by: Konstantin Yarovoy <[email protected]> Co-authored-by: Konstantin Yarovoy <[email protected]> Co-authored-by: Konstantin <[email protected]>
Node drain test not starting due to chaos resources not found
Steps to reproduce
Steps to reproduce the behavior:
$ cnf-testsuite version
CNF TestSuite version: v1.2.0
$ cnf-testsuite node_drain
🎬 Testing: [node_drain]
< not progressing>
$ kubectl get nodes
$ kubectl describe chaosengine -n cnti dns-dserver-1c6b0d96
Chaos operator logs:
Expected behavior
The expectation is that the AUT runner is started and the test is executed.
In cases like this (broken external link), the testsuite shall not run an endless loop and terminate with error instead.
Release tests shall be enhanced to maintain high quality of the releases software.
Device (please complete the following information):
$ uname -a
Linux ip-10-0-33-96 6.5.0-1018-aws #18~22.04.1-Ubuntu SMP Fri Apr 5 17:44:33 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
NOTE: you can enable higher logging level output via the command line or env var. to help with debugging
$ cat /home/ubuntu/.cnf-testsuite/tools/chaos-experiments/node_drain_experiment.yaml
404: Not Found --> The URL https://raw.githubusercontent.com/litmuschaos/chaos-charts/3.6.0/charts/generic/node-drain/experiment.yaml does not exit
The text was updated successfully, but these errors were encountered: