-
Notifications
You must be signed in to change notification settings - Fork 720
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build fail due to apt update failure (GPG error: https://debian.neo4j.org/repo stable/ Release: The following signatures were invalid: BADSIG 26C95CF201182252 Neo Technology Admins <admins@neotechnology.com>) #7987
Comments
I have contacted Neo4j about this issue via the contact-us form. |
I wonder if it's due to the key switch to deal with the deprecated SHA-1 issue |
is there any workaround for this? |
@tbarbugli I suspect that avoid installing anything using the APT addon will work |
Since the issue is no longer reproduced, I'll close it for now. |
I'm getting repeated neo4j.org hash sum mismatches on this build: https://travis-ci.org/ccnmtl/blackrock/builds/248530281
|
The issue appears to have resurfaced. |
@BanzaiMan I confirm that the issue resurfaced: :) |
See also: http://stspg.io/1d8f4b1fd |
It looks like travis-ci/travis-build#1090 was manually deployed to production but not merged to master, so may have then been overwritten by an unrelated PR being merged to travis-build master 3 hours ago (presuming master auto-deploys). |
@edmorley Thanks for pointing that out. A deployment earlier today overwrote that hot fix. I fixed the PR, merged and deployed it to production. The fix should be live now. Please test your builds. Restarting should be sufficient. The neo4j source is unavailable as a result, and we will look at the remedy for this, too. |
I'm closing this again. The PR to remove neo4j apt source has been merged and deployed. The neo4j source needs to be reinstated, but that will be tracked separately in #8002. |
I am currently running into an error similar to #7998 (which was closed as a duplicate of this issue). Any ideas?
|
Those are warnings, not errors. If your builds are failing, they're falling for a different reason. |
Ah yes, thanks for the correction @BanzaiMan. However, the failure that we are seeing does seem to be related to these:
The failure is in an ansible playbook and is failing with the following traceback:
The build passes when |
Resurfaced?
|
As far as I can tell, the entire RIAK repos have gone MIA. Exactly what RIAK is doing I'm not sure though. |
I have started seeing this today,
|
Confirmed, this problem has popped up in one of ours, too.
|
For those arriving here, the issue is already being fixed: |
Is it the same issue? |
Issue resurfaced again for me today (Jan 18, 2018). Confirm Docker builds work locally.
Failed RUN
Errors in build
Warnings earlier in build
|
Recent apt failures are discussed elsewhere. |
I think this is related to the PHP Docker image indicated: docker-library/php#542 Another PHP image deploys fine and it has to do with attempting to install a php module using |
Having exact same issue now.
The terrible thing is that all the crashes are random: we have jobs for PyPy, Python 2.x & several different Python 3.x. Sometimes 2.x fails, sometimes 3.x, sometimes PyPy, sometimes both. |
Also seeing this in a xenial build.
|
Can confirm Xenial distro is suffering from this. |
@itkovian - what you are seeing is a different issue. This issue is about apt-get reporting a bad signature. Your issue is about apt-get failing to acquire a lock. |
Its appeared again:
|
Its appeared again... |
It has appeared again... |
Same for us |
Build #7 - Lin-Buo-Ren/Clean-Filter-for-XML - Travis CI
It happens at least since 2017-06-28T10:17:09Z, while 2017-06-28T09:47:25Z still working
UPDATE: Travis CI Status - Apt failures
UPDATE: According to Travis CI Status a hotfix(?) is in place for this issue
UPDATE: The issue is no longer reproduced after the hotfix
The text was updated successfully, but these errors were encountered: