[JIRA] (JENKINS-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis closed an issue as Not A Defect Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Change By: Stefanos Kalantzis Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis commented on JENKINS-54162 Re: Cannot delete pod that doesn't start properly Jeez... I discovered a "rogue" Jenkins instance that I was not aware was running. You were right the created pods were coming from that Jenkins. Thanks and sorry for any confusion. Please close Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis commented on JENKINS-54162 Re: Cannot delete pod that doesn't start properly I don't know if I'm explaining something wrong here... restart != recreate, right ? I never see restarting pods. They all have restartCount=0. I see pods with status Error (never CrashLoopbackOff), which after a few seconds disappear (the pods). Then new pods appear with different suffix. The total number of pods that simultaneously do this is quite stable, and looks like it is equal to the number of jobs that once started with a misconfigured podTemplate. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis commented on JENKINS-54162 Re: Cannot delete pod that doesn't start properly Well, yes, no new pods will be created. What I'm saying is that the existing ones that were requested by Jenkins, are not able to start, and get in a re-creation loop by kubernetes. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis updated an issue Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Change By: Stefanos Kalantzis If the pod template is misconfigured, and the actual pod container exits with a non-0 code, then kubernetes tries to re-create it, in an endless loop. Mind you that there is no restart count on the pod, it's actually recreated, with a different random suffix.Manually deleting the pod doesn't help, because it was never created successfully, so kubernetes re-creates it again.In our case, the misconfiguration was a wrong JENKINS_URL. Also, when the kubernetes-plugin creates a pod, there isn't any associated type in kubernetes itself (i.e. deployment, replicaset, job, etc...). So there wasn't anything to delete on a higher level.Wouldn't a kubernetes "job" be suitable for this plugin ? (Instead of creating a standalone/orphan pod). This way if something goes wrong then the situation can be rectified by deleting the "job" in kubernetes. I hope I haven't made any wrong assumptions here because I'm quite new to the kubernetes world :)*EDIT*: Forgot to mention that this was happening both with Jenkins alive without any jobs running, AND with Jenkins itself shut down (the whole VM). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to
[JIRA] (JENKINS-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis updated an issue Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Change By: Stefanos Kalantzis If the pod template is misconfigured, and the actual pod container exits with a non-0 code, then kubernetes tries to re-create it, in an endless loop. Mind you that there is no restart count on the pod, it's actually recreated, with a different random suffix.Manually deleting the pod doesn't help, because it was never created successfully, so kubernetes re-creates it again.In our case, the misconfiguration was a wrong JENKINS_URL. Also, when the kubernetes-plugin creates a pod, there isn't any associated type in kubernetes itself (i.e. deployment, replicaset, job, etc...). So there wasn't anything to delete on a higher level.Wouldn't a kubernetes "job" be suitable for this plugin ? (Instead of creating a standalone/orphan pod). This way if something goes wrong then the situation can be rectified by deleting the "job" in kubernetes. I hope I haven't made any wrong assumptions here because I'm quite new to the kubernetes world :) *_EDIT_*: Forgot to mention that this was happening with Jenkins itself shut down (the whole VM). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis edited a comment on JENKINS-54162 Re: Cannot delete pod that doesn't start properly Sorry I forgot to mention this, good point. This is what I initially believed too, but I shut down Jenkins and the re-creation didn't stop. I will edit edited the original post. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis updated an issue Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Change By: Stefanos Kalantzis If the pod template is misconfigured, and the actual pod container exits with a non-0 code, then kubernetes tries to re-create it, in an endless loop. Mind you that there is no restart count on the pod, it's actually recreated, with a different random suffix.Manually deleting the pod doesn't help, because it was never created successfully, so kubernetes re-creates it again.In our case, the misconfiguration was a wrong JENKINS_URL. Also, when the kubernetes-plugin creates a pod, there isn't any associated type in kubernetes itself (i.e. deployment, replicaset, job, etc...). So there wasn't anything to delete on a higher level.Wouldn't a kubernetes "job" be suitable for this plugin ? (Instead of creating a standalone/orphan pod). This way if something goes wrong then the situation can be rectified by deleting the "job" in kubernetes. I hope I haven't made any wrong assumptions here because I'm quite new to the kubernetes world :) * _EDIT_ EDIT *: Forgot to mention that this was happening with Jenkins itself shut down (the whole VM). Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To
[JIRA] (JENKINS-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis commented on JENKINS-54162 Re: Cannot delete pod that doesn't start properly Sorry I forgot to mention this, good point. This is what I initially believed too, but I shut down Jenkins and the re-creation didn't stop. I will edit the original post. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- 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-54162) Cannot delete pod that doesn't start properly
Title: Message Title Stefanos Kalantzis created an issue Jenkins / JENKINS-54162 Cannot delete pod that doesn't start properly Issue Type: Bug Assignee: Carlos Sanchez Components: kubernetes-plugin Created: 2018-10-19 09:45 Environment: Jenkins v2.121.3 kubernetes-plugin v1.12.3 kubernetes 1.7.10 Priority: Critical Reporter: Stefanos Kalantzis If the pod template is misconfigured, and the actual pod container exits with a non-0 code, then kubernetes tries to re-create it, in an endless loop. Mind you that there is no restart count on the pod, it's actually recreated, with a different random suffix. Manually deleting the pod doesn't help, because it was never created successfully, so kubernetes re-creates it again. In our case, the misconfiguration was a wrong JENKINS_URL. Also, when the kubernetes-plugin creates a pod, there isn't any associated type in kubernetes itself (i.e. deployment, replicaset, job, etc...). So there wasn't anything to delete on a higher level. Wouldn't a kubernetes "job" be suitable for this plugin ? (Instead of creating a standalone/orphan pod). This way if something goes wrong then the situation can be rectified by deleting the "job" in kubernetes. I hope I haven't made any wrong assumptions here because I'm quite new to the kubernetes world
[JIRA] (JENKINS-45131) Locking Resources is slow
Title: Message Title Stefanos Kalantzis commented on JENKINS-45131 Re: Locking Resources is slow I can confirm this behavior. I wouldn't classify this as just "slow". In my case I tried to use 10 locks in parallel (with different resource name), and the whole Jenkins environment was unresponsive for about 1.5 hours. Any page I tried to load timed-out. (The build was running on a build node on another VM) Versions: Jenkins - 2.107.1 Lockable Resources - 2.2 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-45131) Locking Resources is slow
Title: Message Title Stefanos Kalantzis edited a comment on JENKINS-45131 Re: Locking Resources is slow I can confirm this behavior.I wouldn't classify this as just "slow".In my case I tried to use 10 locks in parallel (with different resource name), and the whole Jenkins environment was unresponsive for about 1.5 hours. Any page I tried to load timed-out.(The build was running on a build node on another VM) Versions: * Jenkins version - 2.107.1 * Lockable Resources version - 2.2 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.
