[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Ok I seem to have missed it then. Could it be in jenkins itself? At the moment the name field for the container doesn't have a help text. I think it would be really useful to add it there Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master I think it would be useful to add to the documentation that the name of the container for the jnpl agent must be named jnlp. This issue was quite hard to debug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master This was related to this issue. If the name of the custom agent is not `jnlp`, then another agent with the default jnlp image is created. This explains messages like `channel already closed` etc.. Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai commented on JENKINS-49511 Re: Connection fails between agent and master Actually it works if I revert back to JNLP-2. Is there any pointers I could look at that would block JNLP-4 inside kubernetes? Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49510) Failed connections between JNLP agent and master on Kubernetes
Title: Message Title Cesar Tron-Lozai closed an issue as Duplicate Jenkins / JENKINS-49510 Failed connections between JNLP agent and master on Kubernetes Change By: Cesar Tron-Lozai Status: Open Closed Assignee: Carlos Sanchez Cesar Tron-Lozai Resolution: Duplicate Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-49511) Connection fails between agent and master
Title: Message Title Cesar Tron-Lozai created an issue Jenkins / JENKINS-49511 Connection fails between agent and master Issue Type: Bug Assignee: Carlos Sanchez Attachments: logs-from-jnlp-in-slave-with-docker-g2k77.txt, logs-from-master-in-jenkins-67b96c6474-6m6wt.txt Components: kubernetes-plugin Created: 2018-02-12 16:39 Environment: Jenkins: 2.105 Kubernetes-plugin: 1.2 Priority: Major Reporter: Cesar Tron-Lozai I've set up Jenkins to run on a k8s cluster. I'm using the kubernetes plugin to create agent in the cluster. I have a discovery service available at jenkins-discovery.jenkins.svc.cluster.local:5. I've set up the tunnel property to jenkins-discovery.jenkins.svc.cluster.local:5 When I start a job, the agent seems to be able to connect but then fails for some unknown reasons. The agent logs: INFO: Locating server among [http://jenkins-internal.jenkins.svc.cluster.local:8080/] Feb 12, 2018 4:08:37 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-discovery.jenkins.svc.cluster.local Agent port: 5 Identity: a1:e6:e0:d2:ad:30:2e:11:47:4f:0f:95:41:d3:d0:a4 Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Feb
[JIRA] (JENKINS-49510) Failed connections between JNLP agent and master on Kubernetes
Title: Message Title Cesar Tron-Lozai created an issue Jenkins / JENKINS-49510 Failed connections between JNLP agent and master on Kubernetes Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-02-12 16:38 Environment: Jenkins 2.105 Jenkins kubernetes: 1.2 Priority: Major Reporter: Cesar Tron-Lozai I've set up Jenkins to run on a k8s cluster. I'm using the kubernetes plugin to create agent in the cluster. I have a discovery service available at jenkins-discovery.jenkins.svc.cluster.local:5. I've set up the tunnel property to jenkins-discovery.jenkins.svc.cluster.local:5 When I start a job, the agent seems to be able to connect but then fails for some unknown reasons. The agent logs: INFO: Locating server among [http://jenkins-internal.jenkins.svc.cluster.local:8080/] Feb 12, 2018 4:08:37 PM org.jenkinsci.remoting.engine.JnlpAgentEndpointResolver resolve INFO: Remoting server accepts the following protocols: [JNLP4-connect, Ping] Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Agent discovery successful Agent address: jenkins-discovery.jenkins.svc.cluster.local Agent port: 5 Identity: a1:e6:e0:d2:ad:30:2e:11:47:4f:0f:95:41:d3:d0:a4 Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Handshaking Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Connecting to jenkins-discovery.jenkins.svc.cluster.local:5 Feb 12, 2018 4:08:37 PM hudson.remoting.jnlp.Main$CuiListener status INFO: Trying protocol: JNLP4-connect Feb 12, 2018 4:08:37 PM
[JIRA] (JENKINS-43067) Cannot create nodes from Cloud Configuration since Jenkins 2.51
Title: Message Title Cesar Tron-Lozai closed an issue as Not A Defect Jenkins / JENKINS-43067 Cannot create nodes from Cloud Configuration since Jenkins 2.51 Change By: Cesar Tron-Lozai Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43067) Cannot create nodes from Cloud Configuration since Jenkins 2.51
Title: Message Title Cesar Tron-Lozai commented on JENKINS-43067 Re: Cannot create nodes from Cloud Configuration since Jenkins 2.51 This is an issue with AWS and the ECS plugin Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43067) Cannot create nodes from Cloud Configuration since Jenkins 2.51
Title: Message Title Cesar Tron-Lozai updated an issue Jenkins / JENKINS-43067 Cannot create nodes from Cloud Configuration since Jenkins 2.51 Change By: Cesar Tron-Lozai Priority: Blocker Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-43067) Cannot create nodes from Cloud Configuration since Jenkins 2.51
Title: Message Title Cesar Tron-Lozai created an issue Jenkins / JENKINS-43067 Cannot create nodes from Cloud Configuration since Jenkins 2.51 Issue Type: Bug Assignee: Unassigned Components: core Created: 2017/Mar/23 11:58 AM Labels: cloud node Priority: Blocker Reporter: Cesar Tron-Lozai Since I've upgraded to 2.51 I cannot build jobs running on Slave provided by my Cloud. I use the Amazon-ecs-plugin (https://wiki.jenkins-ci.org/display/JENKINS/Amazon+EC2+Container+Service+Plugin) to generate Nodes on demand. It has been working for months. Now the builds get stuck at: Still waiting to schedule task Jenkins doesn’t have label docker I have a valid cloud configuration that provides Nodes for the label `Docker` Add Comment
[JIRA] (JENKINS-36217) Must update IAM roles in the documetnation
Title: Message Title
Cesar Tron-Lozai created an issue
Jenkins / JENKINS-36217
Must update IAM roles in the documetnation
Issue Type:
Task
Assignee:
Jan Roehrich
Components:
amazon-ecs-plugin
Created:
2016/Jun/24 4:20 PM
Environment:
jenkins: 2.9, Amazon EC2 Container Service plugin: 1.3
Priority:
Major
Reporter:
Cesar Tron-Lozai
The privileges listed in the documentation are not enough to successfully start a task in the ECS cluster. The resources "arn:aws:ecs:::task-definition/jenkins-slave:*" must be added. For example: { "Version": "2012-10-17", "Statement": [ { "Sid": "Stmt1452746887373", "Action": [ "ecs:DescribeClusters", "ecs:RunTask", "ecs:StopTask" ], "Effect": "Allow", "Resource": [ "arn:aws:ecs:::cluster/", "arn:aws:ecs:::task-definition/jenkins-slave:*" ] } , { "Sid": "Stmt1452779658000", "Effect": "Allow", "Action": [ "ecs:RegisterTaskDefinition", "ecs:ListClusters" ], "Resource": [ "*" ] } ] }
Add Comment
[JIRA] (JENKINS-33731) iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: *
Title: Message Title Cesar Tron-Lozai commented on JENKINS-33731 Re: iam user is not authorized to perform: ecs:RegisterTaskDefinition on resource: * I had the same issue. This is a mistake in the documentation. You should add the following resources in your AWS policy: "arn:aws:ecs:::task-definition/jenkins-slave:*" I found this by connecting to my instance and using aws ecs commands Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
