[JIRA] (JENKINS-60286) durable-task v1.33 fails with agent Dockerfile

[marky.r.jack...@gmail.com (JIRA)]

Title: Message Title

Marky Jackson commented on JENKINS-60286   Re: durable-task v1.33 fails with agent Dockerfile Devin Nusbaum here is the build log from the console. I eventually have to hard kill the job because it just hangs at the missing file: Started by user mark.jack...@sysdig.com 15:51:39 Connecting to https://api.github.com using xxxxxxx/****** (zzzzzzzzz) Obtained Jenkinsfile from xxxxxxx Running in Durability level: MAX_SURVIVABILITY [Pipeline] Start of Pipeline [Pipeline] node Running on EC2 (ec2) - ${WORKER_NAME} (ec2ID) in /home/${USER}/workspace/ntend-pipeline_customer-settings [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Checkout SCM) [Pipeline] checkout using credential ${TOKEN} Cloning the remote Git repository Cloning repository ${REPO} > git init /home/${USER}/workspace/ntend-pipeline_customer-settings # timeout=10 } Fetching upstream changes from ${REPO} > git --version # timeout=10 } using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress -- ${REPO} +refs/heads/*:refs/remotes/origin/* # timeout=10 } Checking out Revision ${REVISION} (customer-settings) Commit message: "Reverting my changes" > git config remote.origin.url ${REPO} # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url ${REPO} # timeout=10 Fetching upstream changes from ${REPO} using GIT_SSH to set credentials ${TOKEN} > git fetch --tags --progress --${REPO} +refs/heads/customer-settings:refs/remotes/origin/customer-settings # timeout=10 > git config core.sparsecheckout # timeout=10 > git checkout -f ${REVISION} # timeout=10 > git rev-list --no-walk ${REVISION} # timeout=10 [Pipeline] } [Pipeline] // stage [Pipeline] withEnv [Pipeline] { [Pipeline] stage [Pipeline] { (Declarative: Agent Setup) [Pipeline] isUnix [Pipeline] readFile [Pipeline] sh + docker build -t c7c9f201c0dbb37091ac75c689812beae3bf54b4 -f Dockerfile . WARNING: Error loading config file: /home/${USER}/.docker/config.json: EOF Sending build context to Docker daemon 116.3MBStep 1/13 : FROM ubuntu:latest ---> 775349758637 Step 2/13 : ENV DEBIAN_FRONTEND=noninteractive ---> Using cache ---> 08bb415b8561 Step 3/13 : RUN apt-get update -y && apt-get install apt-transport-https ca-certificates curl gnupg git python-pip python2.7 python2.7-dev groff-base build-essential parallel jq grep awscli -y --no-install-recommends ---> Using cache ---> 2d2f267ee29f Step 4/13 : RUN groupadd ${USER} -g 500 ---> Using cache ---> c1508155cdc1 Step 5/13 : RUN useradd -m -d /home/${USER} -g ${USER} -u 500 ${USER} ---> Using cache ---> 12ad008b1a8a Step 6/13 : RUN curl -sSL https://dl.google.com/linux/linux_signing_key.pub | apt-key add - && echo "deb [arch=amd64] https://dl.google.com/linux/chrome/deb/ stable main" > /etc/apt/sources.list.d/google-chrome.list ---> Using cache ---> 1e4d342560b2 Step 7/13 : RUN curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add - ---> Using cache ---> 7ae11025dc8e Step 8/13 : RUN echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list ---> Using cache ---> 6f40d90e286a Step 9/13 : ENV YARN_VERSION=1.17.3-1 ---> Using cache ---> 818b40b458e3 Step 10/13 : RUN apt-get update && apt-get install -y yarn=$YARN_VERSION --no-install-recommends ---> Using cache ---> 88de9a37077f Step 11/13 : RUN apt-get update && apt-get install -y google-chrome-stable ---> Using cache ---> f57b038effc4 Step 12/13 : ENV NODE_VERSION=10.16.3 ---> Using cache ---> 4c946687c3a9 Step 13/13 : RUN curl https://deb.nodesource.com/node_10.x/pool/main/n/nodejs/nodejs_$NODE_VERSION-1nodesource1_amd64.deb > node.deb && dpkg -i node.deb && rm node.deb ---> Using cache ---> 412afce72a56 Successfully built 412afce72a56 Successfully tagged c7c9f201c0dbb37091ac75c689812beae3bf54b4:latest [Pipeline] } [Pipeline] // stage [Pipeline] isUnix [Pipeline] sh + docker inspect -f . c7c9f201c0dbb37091ac75c689812beae3bf54b4 WARNING: Error loading config file: /home/${USER}/.docker/config.json: EOF . [Pipeline] withDockerContainer EC2 (ec2) - ${LABEL} ($EC2-ID) does not seem to be running inside a container $ docker run -t -d -u 500:500 -w /home/${USER}/workspace/ntend-pipeline_customer-settings -v /home/$USER}/workspace/ntend-pipeline_customer-settings:/home/${USER}/workspace/ntend-pipeline_customer-settings:rw,z -v /home/${USER}/workspace/ntend-pipeline_customer-settings@tmp:/home/${USER}/workspace/ntend-pipeline_customer-settings@tmp:rw,z -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** -e ******** c7c9f201c0dbb37091ac75c689812beae3bf54b4 cat $ docker top 96ac75a6873563bc96ddef48328caaa3a641987e2d9d7ce10b86db07c2ee6876 -eo pid,comm [Pipeline] { [Pipeline] withCredentials Masking supported pattern matches of $NPM_AUTH_TOKEN or $GITHUB_ACCESS_TOKEN [Pipeline] { [Pipeline] sh process apparently never started in /home/${USER}/workspace/ntend-pipeline_customer-settings@tmp/durable-d4083a8e (running Jenkins temporarily with -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.LAUNCH_DIAGNOSTICS=true might make the problem clearer) Cannot contact EC2 (ec2) - ${LABEL} (${EC2-ID}): java.io.FileNotFoundException: File '/home/${USER}/workspace/ntend-pipeline_customer-settings@tmp/durable-d4083a8e/output.txt' does not exist Hard kill!GitHub has been notified of this commit’s build resultFinished: ABORTED Add Comment   This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f) -- 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.203277.1574777832000.7289.1574784300496%40Atlassian.JIRA.