See
Agent is not connected after 30 attempts, status: Running
check your agent pod logs for errors. They should also show in the jenkins
master log
On Tue, Nov 13, 2018 at 11:36 PM Yaramada Surya tej <yrsu...@gmail.com>
wrote:
> Here is the error logs while using custom image
>
> Error in provisioning; agent=KubernetesSlave name: eks-cluster-qwx9k,
> template=PodTemplate{inheritFrom='', name='eks-cluster', namespace='',
> slaveConnectTimeout=30, label='eks-cluster', nodeSelector='',
> nodeUsageMode=NORMAL, workspaceVolume=EmptyDirWorkspaceVolume
> [memory=false], containers=[ContainerTemplate{name='jnlp', image='
> 99999999999.dkr.ecr.us-east-1.amazonaws.com/jenkinsci-jnlp-slave',
> workingDir='/home/jenkins', command='', args='cat', ttyEnabled=true,
> resourceRequestCpu='', resourceRequestMemory='', resourceLimitCpu='',
> resourceLimitMemory='',
> livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@4a17bf41},
> ContainerTemplate{name='kubectl-helm', image='
> 250312325083.dkr.ecr.us-east-1.amazonaws.com/kubectl-helm:latest',
> workingDir='/home/jenkins', command='/bin/sh -c', args='cat',
> ttyEnabled=true, resourceRequestCpu='', resourceRequestMemory='',
> resourceLimitCpu='', resourceLimitMemory='',
> livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@3a0ad6a5},
> ContainerTemplate{name='java-base-image', image='
> 99999999999.dkr.ecr.us-east-1.amazonaws.com/java8:latest',
> workingDir='/home/jenkins', command='/bin/sh -c', args='cat',
> ttyEnabled=true, resourceRequestCpu='', resourceRequestMemory='',
> resourceLimitCpu='', resourceLimitMemory='',
> livenessProbe=org.csanchez.jenkins.plugins.kubernetes.ContainerLivenessProbe@42ca15d6}],
> yaml=} java.lang.IllegalStateException: Agent is not connected after 30
> attempts, status: Running at
> org.csanchez.jenkins.plugins.kubernetes.KubernetesLauncher.launch(KubernetesLauncher.java:190)
> at hudson.slaves.SlaveComputer$1.call(SlaveComputer.java:294) at
> jenkins.util.ContextResettingExecutorService$2.call(ContextResettingExecutorService.java:46)
> at
> jenkins.security.ImpersonatingExecutorService$2.call(ImpersonatingExecutorService.java:71)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266) at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
> at java.lang.Thread.run(Thread.java:748) Nov 13, 2018 7:58:06 PM INFO
> org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate
> Terminating Kubernetes instance for agent eks-cluster-qwx9k Nov 13, 2018
> 7:58:06 PM WARNING io.fabric8.kubernetes.client.Config tryServiceAccount
> Error reading service account token from: [/var/run/secrets/
> kubernetes.io/serviceaccount/token]. Ignoring. Nov 13, 2018 7:58:06 PM
> INFO okhttp3.internal.platform.Platform log ALPN callback dropped: HTTP/2
> is disabled. Is alpn-boot on the boot class path? Nov 13, 2018 7:58:06 PM
> INFO org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave deleteSlavePod
> Terminated Kubernetes instance for agent default/eks-cluster-qwx9k Nov 13,
> 2018 7:58:06 PM INFO
> org.csanchez.jenkins.plugins.kubernetes.KubernetesSlave _terminate
> Disconnected computer eks-cluster-qwx9k Nov 13, 2018 7:58:09 PM INFO
> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision Excess
> workload after pending Kubernetes agents: 1 Nov 13, 2018 7:58:09 PM INFO
> org.csanchez.jenkins.plugins.kubernetes.KubernetesCloud provision Template
> for label eks-cluster: Kubernetes Pod Template Nov 13, 2018 7:58:09 PM
> WARNING io.fabric8.kubernetes.client.Config tryServiceAccount Error reading
> service account token from: [/var/run/secrets/
> kubernetes.io/serviceaccount/token]. Ignoring. Nov 13, 2018 7:58:09 PM
> INFO okhttp3.internal.platform.Platform log ALPN callback dropped: HTTP/2
> is disabled. Is alpn-boot on the boot class path? Nov 13, 2018 7:58:09 PM
> INFO hudson.slaves.NodeProvisioner$StandardStrategyImpl apply Started
> provisioning Kubernetes Pod Template from kubernetes with 1 executors.
> Remaining excess workload: 0 Nov 13, 2018 7:58:19 PM WARNING
> io.fabric8.kubernetes.client.Config tryServiceAccount Error reading service
> account token from: [/var/run/secrets/kubernetes.io/serviceaccount/token].
> Ignoring. Nov 13, 2018 7:58:19 PM INFO hudson.slaves.NodeProvisioner$2 run
> Kubernetes Pod Template provisioning successfully completed. We have now 3
> computer(s) Nov 13, 2018 7:58:19 PM INFO okhttp3.internal.platform.Platform
> log ALPN callback dropped: HTTP/2 is disabled. Is alpn-boot on the boot
> class path?
>
> On Tuesday, 13 November 2018 01:06:24 UTC-5, Yaramada Surya tej wrote:
>>
>> Hi, I am trying to use custom image which is based on amazonlinux and
>> pushed to ECR for running jenkins executors on AWS EKS. able to use
>> default image ( alpine) but need help to configure in settings for using a
>> custom image.
>>
>> To achieve this do we need 2 custom images? one for pod and another for
>> container image?
>>
>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/e928b478-dba5-4ef1-ad36-89fc51d0cc30%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/e928b478-dba5-4ef1-ad36-89fc51d0cc30%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-users/CALHFn6MvipKtakJGifBLy223HVd4yfF9aORekn3B-ckigkoUAA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
