Closed cfra closed 1 year ago
Hi there,
We have found that there's a problem with the logs. Depending on which situation applies follow one, some or all of these instructions.
If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.
The log is too long to be included in a GitHub comment, so I uploaded it here: https://nowhere.ws/dump/renovatelog.txt
Trim the log to the relevant branch, where the error occures. We don't have time to search such big logs. 😕
I am sorry @viceice - I can understand your frustration, I just did not know how to filter the log properly.
I have trimmed it to the problematic branch now and hope I haven't dropped relevant information in the process:
This is the stdout
, formatted:
installing v2 tool node v18.12.0
linking tool node v18.12.0
node: v18.12.0 /usr/local/bin/node
npm: 8.19.2 /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 7 seconds
skip cleanup, not a docker build: fad8b4ca1d43
installing v2 tool npm v6.14.17
added 1 package in 16s
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated fs-access@2.0.0: This package is no longer relevant as Node.js 0.12 is unmaintained.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
added 397 packages, removed 13 packages, and changed 18 packages in 38s
linking tool npm v6.14.17
6.14.17
Installed v2 /usr/local/buildpack/tools/v2/npm.sh in 58 seconds
skip cleanup, not a docker build: fad8b4ca1d43
and the stack:
ExecError: Command failed: docker run --rm --name=renovate_sidecar --label=renovate_child -v \"/mnt/renovate/gh/PicturePipe/hatch\":\"/mnt/renovate/gh/PicturePipe/hatch\" -v \"/tmp/renovate-cache\":\"/tmp/renovate-cache\" -v \"/tmp/containerbase\":\"/tmp/containerbase\" -e NPM_CONFIG_CACHE -e npm_config_store -e BUILDPACK_CACHE_DIR -e CONTAINERBASE_CACHE_DIR -w \"/mnt/renovate/gh/PicturePipe/hatch\" docker.io/renovate/sidecar bash -l -c \"install-tool node v18.12.0 && install-tool npm 6.14.17 && hash -d npm 2>/dev/null || true && npm install --no-audit --ignore-scripts && npm dedupe\"
at ChildProcess.<anonymous> (/home/ubuntu/renovateapp/node_modules/renovate/dist/util/exec/common.js:87:24)
at ChildProcess.emit (node:events:525:35)
at ChildProcess.emit (node:domain:489:12)
at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
So it's also not clear from npm
about why it exited with an error. I tried reproducing to see if installing npm v6 into node 18 failed:
❯ docker run --rm -it containerbase/sidecar
ubuntu@9ab849c603ba:/$ install-tool node v18.12.0
installing v2 tool node v18.12.0
linking tool node v18.12.0
node: v18.12.0 /usr/local/bin/node
npm: 8.19.2 /usr/local/bin/npm
Installed v2 /usr/local/buildpack/tools/v2/node.sh in 11 seconds
skip cleanup, not a docker build: 9ab849c603ba
ubuntu@9ab849c603ba:/$ install-tool npm v6.14.17 && echo "success"
installing v2 tool npm v6.14.17
added 1 package in 27s
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.
npm WARN deprecated fs-access@2.0.0: This package is no longer relevant as Node.js 0.12 is unmaintained.
npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142
added 397 packages, removed 13 packages, and changed 18 packages in 55s
linking tool npm v6.14.17
6.14.17
Installed v2 /usr/local/buildpack/tools/v2/npm.sh in 91 seconds
skip cleanup, not a docker build: 9ab849c603ba
success
ubuntu@9ab849c603ba:/$
So it seems like the npm install --no-audit --ignore-scripts
is either not running or it's showing no logs
Running the following locally on the jquery renovate branch where artifact updating fails seems to work fine and returns with EXIT_SUCCESS
(0):
docker run --rm --name=renovate_sidecar --label=renovate_child \
-v "$(pwd):/mnt/renovate/gh/PicturePipe/hatch" \
-e NPM_CONFIG_CACHE \
-e npm_config_store \
-e BUILDPACK_CACHE_DIR \
-e CONTAINERBASE_CACHE_DIR \
-w /mnt/renovate/gh/PicturePipe/hatch docker.io/renovate/sidecar \
bash \
-l \
-c "install-tool node v18.12.0 && install-tool npm 6.14.17 && hash -d npm 2>/dev/null || true && npm install --no-audit --ignore-scripts && npm dedupe"
The renovate cache and the containerbase from /tmp
are both missing here though, so I am not sure how comparable that is.
Hey @cfra @rarkins ,
I'm facing the same or a similar issue since a couple of days. Renovate no longer can update the package.-lock.json
. I'm using the following docker image: renovate/renovate:34.24
with the config RENOVATE_BINARY_SOURCE="install"
. The package-lock.json
has the lockfileVersion 2.
This is the snippet of the debug log.
DEBUG: manager.getUpdatedPackageFiles() reuseExistingBranch=false (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: npm.updateDependency(): devDependencies.mini-css-extract-plugin = 2.7.0 (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Updating mini-css-extract-plugin in Scripts/package.json (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Updated 1 package files (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Getting updated lock files (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Writing package.json files (repository=group/project, branch=renovate/all-minor-patch)
"packageFiles": [
"Scripts/package.json"
]
DEBUG: Writing Scripts/package-lock.json (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Massaging npm lock file before writing to disk (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Writing any updated package files (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Writing Scripts/package.json (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: npmrc file found in repository (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Writing updated .npmrc file to Scripts/.npmrc (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Generating package-lock.json for Scripts (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Spawning npm install to create Scripts/package-lock.json (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Updating lock file only (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: No node constraint found - using latest (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Setting CONTAINERBASE_CACHE_DIR to /builds/group/renovate-bot/renovate/cache/containerbase (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Using containerbase dynamic installs (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: GET https://nodejs.org/dist/index.json = (code=SELF_SIGNED_CERT_IN_CHAIN, statusCode=-1 retryCount=0, duration=290) (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Datasource connection error (repository=group/project, branch=renovate/all-minor-patch)
"datasource": "node",
"packageName": "node",
"url": undefined,
"errCode": "SELF_SIGNED_CERT_IN_CHAIN"
DEBUG: lock file error (repository=group/project, branch=renovate/all-minor-patch)
"err": {
"message": "No tool releases found.",
"stack": "Error: No tool releases found.\n at resolveConstraint (/usr/src/app/node_modules/renovate/lib/util/exec/containerbase.ts:190:11)\n at runMicrotasks (<anonymous>)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at generateInstallCommands (/usr/src/app/node_modules/renovate/lib/util/exec/containerbase.ts:241:27)\n at prepareRawExec (/usr/src/app/node_modules/renovate/lib/util/exec/index.ts:145:11)\n at exec (/usr/src/app/node_modules/renovate/lib/util/exec/index.ts:172:39)\n at Object.generateLockFile (/usr/src/app/node_modules/renovate/lib/modules/manager/npm/post-update/npm.ts:124:5)\n at getAdditionalFiles (/usr/src/app/node_modules/renovate/lib/modules/manager/npm/post-update/index.ts:545:17)\n at processBranch (/usr/src/app/node_modules/renovate/lib/workers/repository/update/branch/index.ts:432:31)\n at writeUpdates (/usr/src/app/node_modules/renovate/lib/workers/repository/process/write.ts:160:17)\n at update (/usr/src/app/node_modules/renovate/lib/workers/repository/process/extract-update.ts:151:11)\n at Object.renovateRepository (/usr/src/app/node_modules/renovate/lib/workers/repository/index.ts:61:19)\n at attributes.repository (/usr/src/app/node_modules/renovate/lib/workers/global/index.ts:173:11)\n at Object.start (/usr/src/app/node_modules/renovate/lib/workers/global/index.ts:158:7)\n at /usr/src/app/node_modules/renovate/lib/renovate.ts:17:22"
},
"type": "npm"
DEBUG: No updated lock files in branch (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Branch timestamp: 2022-11-16T20:13:42.802Z (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: PR is older than 2 hours, raise PR with lock file errors (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: 1 file(s) to commit (repository=group/project, branch=renovate/all-minor-patch)
DEBUG: Preparing files for committing to branch renovate/all-minor-patch (repository=group/project, branch=renovate/all-minor-patch)
@xC0dex SELF_SIGNED_CERT_IN_CHAIN
Do you use a proxy? You need to configure additional root certificates for self signed certificates. So you have a different Problem. Please open a new Discussion^1 for more help.
I was affected by this bug too. It seems to be working again with the latest version.
Hi. Any updates here? I'm still facing this issue Also, this discussion seems like describes a similar issue https://github.com/renovatebot/renovate/discussions/15755
Hi there,
Get your issue fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.
Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.
To get started, please read our guide on creating a minimal reproduction.
We may close the issue if you, or someone else, haven't created a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.
Good luck,
The Renovate team
Let's have a reproduction repo to debug if it's still happening for anyone
I had the same issue and was able to resolve it by adding the following config to the gitlab-ci.yml:
RENOVATE_CUSTOM_ENV_VARIABLES: '{"PIP_CERT": "/etc/ssl/certs/ca-certificates.crt", "TWINE_CERT": "/etc/ssl/certs/ca-certificates.crt", "REQUESTS_CA_BUNDLE": "/etc/ssl/certs/ca-certificates.crt", "CURL_CA_BUNDLE": "/etc/ssl/certs/ca-certificates.crt", "SSL_CERT_FILE": "/etc/ssl/certs/ca-certificates.crt", "NODE_EXTRA_CA_CERTS": "/etc/ssl/certs/ca-certificates.crt"}'
Would it make sense to add this information to the docs? https://docs.renovatebot.com/examples/self-hosting/#self-signed-tlsssl-certificates
When a bug has been marked as needing a reproduction, it means nobody can work on it until one is provided. In cases where no reproduction is possible, or the issue creator does not have the time to reproduce, we unfortunately need to close such issues as they are non-actionable and serve no benefit by remaining open. This issue will be closed after 7 days of inactivity.
This bug report has been closed as we need a reproduction to work on this. If the original poster or anybody else with the same problem discovers that they can reproduce it, please create a new issue, and reference this issue.
How are you running Renovate?
Mend Renovate hosted app on github.com
If you're self-hosting Renovate, tell us what version of Renovate you run.
No response
If you're self-hosting Renovate, select which platform you are using.
No response
If you're self-hosting Renovate, tell us what version of the platform you run.
No response
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
Describe the bug
After recent updates, renovate started to fail javascript dependency updates with an "Artifact update problem" for
package-lock.json
.Looking at the changes from the updates, it seems
package.json
gets updated, butpackage-lock.json
does not.The section "failure details" in the "Artifact update problem" comment is completely empty, and the only warning/error information that I can find in the Renovate log is that updating
package-lock.json
failed, with no information as to why it happened.This for example affects PR#1697 on PicturePipe/hatch
Relevant debug logs
Logs
``` Copy/paste the relevant log(s) here, between the starting and ending backticks ```Have you created a minimal reproduction repository?
No reproduction repository