You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@yunikorn.apache.org by "Chia-Ping Tsai (Jira)" <ji...@apache.org> on 2024/02/02 08:35:00 UTC

[jira] [Created] (YUNIKORN-2377) fix "kubectl: executable file not found in $PATH" for e2e

Chia-Ping Tsai created YUNIKORN-2377:
----------------------------------------

             Summary: fix "kubectl: executable file not found in $PATH" for e2e
                 Key: YUNIKORN-2377
                 URL: https://issues.apache.org/jira/browse/YUNIKORN-2377
             Project: Apache YuniKorn
          Issue Type: Bug
            Reporter: Chia-Ping Tsai


{code:java}
  Logging yk fullstatedump, spec: Test_With_Spark_Jobs
  Created log file: /home/chia7712/project/yunikorn-k8shim/build/e2e/spark_jobs_scheduling/Test_With_Spark_Jobs_ykFullStateDump.json
Handling connection for 9080
  Logging k8s cluster info, spec: Test_With_Spark_Jobs
  Created log file: /home/chia7712/project/yunikorn-k8shim/build/e2e/spark_jobs_scheduling/Test_With_Spark_Jobs_k8sClusterInfo.txt
  Failed to log namespace info, ns:spark-qlje7ea5p1, err: exec: "kubectl": executable file not found in $PATH {code}
I observed the error message "kubectl: executable file not found in $PATH" from e2e test. In the e2e we call the "kubectl" command by shell ([https://github.com/apache/yunikorn-k8shim/blob/master/test/e2e/framework/helpers/k8s/k8s_utils.go#L637]), and hence it will cause the error if the node running the e2e does not install the kubectl.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@yunikorn.apache.org
For additional commands, e-mail: issues-help@yunikorn.apache.org