e the
>>>>>>>>>> same behavior, right?
>>>>>>>>>>
>>>>>>>>>> Thanks.
>>>>>>>>>>
>>>>>>>>>> Hong
>>>>>>>>>>
>>>
>>>>>> Hello Carlos,
>>>>>>>>>>
>>>>>>>>>> Thanks for reply again.
>>>>>>>>>> And I obviously have jenkins service expose in namespace
>>>>>>>>>> &q
> *8080*:30808/TCP,8443:30443/TCP,5:30500/TCP
>>>>>>>>> 15h
>>>>>>>>>
>>>>>>>>> In my working environment, there are seems some DNS issue.
>>>>>>>>> So for example, I us
ent.java:558)
>>>>>>>>>> at sun.net.www.http.HttpClient.(HttpClient.java:242)
>>>>>>>>>> at sun.net.www.http.HttpClient.New(HttpClient.java:339)
>>>>>>>>>> at sun.net.www.http.HttpClient.Ne
t;>>> ------------
>>>>>>>
>>>>>>> So in podTemplate, is there any similar syntax like above?
>>>>>>> And that could solve *jenkins.build-env.sv
t;>>>>> issue in container JNLP of slave?
>>>>>>
>>>>>> But, if the service ip address of Jenkins is not static, that is
>>>>>> still a problem in my environment...
>>>>>> Thanks.
>>>>>>
>>>>&g
t;>
>>>>>> you are correct your kubernetes DNS can't resolve the name, assuming
>>>>>> you have a service jenkins in the build-env namespace
>>>>>>
>>>>>> On Thu, Oct 5, 2017 at 4:09 PM, WANG, YAN-HONG <allway...@g
t;> Jenkins plugin (kubernetes: *1.0*).
>>>>>> Kuberntes Server: *v1.7.7* ( One master and one minion)
>>>>>> Platform: Ubuntu 16.04 (in *Synnefo *cluster environment)
>>>>>>
>>>>>> When I execute pipeline job
t;>>>> *$ ​kubectl --namespace=build-env logs slave-jksnf-q6dlr jnlp*
>>>>> Warning: JnlpProtocol3 is disabled by default, use JNLP_PROTOCOL_OPTS
>>>>> to alter the behavior
>>>>> Warn
t;>> to alter the behavior
>>>> Warning: SECRET is defined twice in command-line arguments and the
>>>> environment variable
>>>> Warning: AGENT_NAME is defined twice in command-line arguments and the
>>>> environment variable
>>>> Oct 0
n.remoting.jnlp.Main$CuiListener
>>> INFO: Jenkins agent is running in headless mode.
>>> Oct 05, 2017 1:29:32 PM hudson.remoting.Engine startEngine
>>> WARNING: No Working Directory. Using the legacy JAR Cache location:
>>> /home/jenkins/.jenkins/cache/ja
JAR Cache location:
>> /home/jenkins/.jenkins/cache/jars
>> Oct 05, 2017 1:29:32 PM hudson.remoting.jnlp.Main$CuiListener status
>> INFO: Locating server among [
>> http://jenkins.build-env.svc.cluster.local:8080/]
>> Oct 05, 2017 1:29:37 PM hudson.remoting.jnlp.Main$CuiListener
you are correct your kubernetes DNS can't resolve the name, assuming you
have a service jenkins in the build-env namespace
On Thu, Oct 5, 2017 at 4:09 PM, WANG, YAN-HONG
wrote:
> Hello,
>
> My environment:
> Jenkins: 2.73.1
> Jenkins plugin (kubernetes: *1.0*).
>
2017 1:29:37 PM hudson.remoting.jnlp.Main$CuiListener error
SEVERE: Failed to connect to
http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAgentListener/:
jenkins.build-env.svc.cluster.local
java.io.IOException: Failed to connect to
http://jenkins.build-env.svc.cluster.local:8080/tcpSlaveAge
14 matches
Mail list logo