[JIRA] (JENKINS-58766) kubernetes-plugin access denied after update to 1.18.0

[seck...@in.tum.de (JIRA)]

Title: Message Title

Steffen Seckler updated an issue   Jenkins / JENKINS-58766 kubernetes-plugin access denied after update to 1.18.0 Change By: Steffen Seckler After updating to kubernetes-plugin 1.18.0 I got an error when using the old /home/jenkins directory inside of a pod template definition. Using /home/jenkins/agent in the pod templates worked, however. The error was: ``` Also:   hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from ............(hidden).............   at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1743)   at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:357)   at hudson.remoting.Channel.call(Channel.java:957)   at hudson.FilePath.act(FilePath.java:1072)   at hudson.FilePath.act(FilePath.java:1061)   at hudson.FilePath.mkdirs(FilePath.java:1246)   at hudson.plugins.git.GitSCM.createClient(GitSCM.java:821)   at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1169)   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep.checkout(SCMStep.java:124)   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:93)   at org.jenkinsci.plugins.workflow.steps.scm.SCMStep$StepExecutionImpl.run(SCMStep.java:80)   at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)   at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)   at java.util.concurrent.FutureTask.run(FutureTask.java:266)   at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)   at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)   at java.lang.Thread.run(Thread.java:745) java.nio.file.AccessDeniedException: /home/jenkins/workspace at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) at sun.nio.fs.UnixFileSystemProvider.createDirectory(UnixFileSystemProvider.java:384) at java.nio.file.Files.createDirectory(Files.java:674) at java.nio.file.Files.createAndCheckIsDirectory(Files.java:781) at java.nio.file.Files.createDirectories(Files.java:767) at hudson.FilePath.mkdirs(FilePath.java:3239) at hudson.FilePath.access$1300(FilePath.java:212) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1254) at hudson.FilePath$Mkdirs.invoke(FilePath.java:1250) at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) at hudson.remoting.UserRequest.perform(UserRequest.java:212) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:369) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) 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 hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93) at java.lang.Thread.run(Thread.java:748) Finished: FAILURE ``` This might have sth. to do with using the default jnlp container that most likely now uses the new directory `/home/jenkins/agent` ) and custom additional containers still using the old home directory `/home/jenkins`. **Steps to reproduce** 1. create pod template with default jnlp container by not specifying said jnlp container 2. add an additional container using /home/jenkins as home directory ** Workaround** Use the new default directory /home/jenkins/agent in all containers ** Related Issues/PR** https://issues.jenkins-ci.org/browse/JENKINS-58705 https://github.com/jenkinsci/kubernetes-plugin/pull/559 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. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.201071.1564670804000.5533.1564671000411%40Atlassian.JIRA.