Lukasz Gajowy created BEAM-6476:
-----------------------------------

             Summary: Kubectl command missing on workers beam8 and beam11
                 Key: BEAM-6476
                 URL: https://issues.apache.org/jira/browse/BEAM-6476
             Project: Beam
          Issue Type: Bug
          Components: testing
            Reporter: Lukasz Gajowy
            Assignee: Jason Kuster


Kubernetes seems to have gone missing on beam8 and beam11 leading to 
Performance Tests failures: 


[https://builds.apache.org/view/A-D/view/Beam/view/PerformanceTests]


{code:java}
...
[EnvInject] - Variables injected successfully.
[beam_PerformanceTests_JDBC] $ /bin/bash -xe /tmp/jenkins5453785317279275290.sh
+ gcloud container clusters get-credentials io-datastores --zone=us-central1-a 
--verbosity=debug
DEBUG: Running [gcloud.container.clusters.get-credentials] with arguments: 
[--verbosity: "debug", --zone: "us-central1-a", NAME: "io-datastores"]
WARNING: Accessing a Kubernetes Engine cluster requires the kubernetes 
commandline
client [kubectl]. To install, run
  $ gcloud components install kubectl

Fetching cluster endpoint and auth data.
DEBUG: Saved kubeconfig to /home/jenkins/.kube/config
kubeconfig entry generated for io-datastores.
INFO: Display format: "default"
DEBUG: SDK update checks are disabled.
[beam_PerformanceTests_JDBC] $ /bin/bash -xe /tmp/jenkins5922335513066151017.sh
+ cp /home/jenkins/.kube/config 
/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_JDBC/config-beam-performancetests-jdbc-1603
[beam_PerformanceTests_JDBC] $ /bin/bash -xe /tmp/jenkins693655582377630528.sh
+ kubectl 
--kubeconfig=/home/jenkins/jenkins-slave/workspace/beam_PerformanceTests_JDBC/config-beam-performancetests-jdbc-1603
 create namespace beam-performancetests-jdbc-1603
/tmp/jenkins693655582377630528.sh: line 2: kubectl: command not found
Build step 'Execute shell' marked build as failure
Sending e-mails to: [email protected]
Finished: FAILURE
{code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to