Mbed-os: Travis: rabbitmq signature failure

Created on 3 Dec 2018  路  5Comments  路  Source: ARMmbed/mbed-os

Description

Experiencing failures since the last weekend.

The command "W: Failed to fetch https://packagecloud.io/rabbitmq/rabbitmq-server/ubuntu/dists/trusty/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY F6609E60XXXXXXX" failed. Retrying, 2 of 3.

key was changed in the msg above F6609E60XXXXXXX (the original one can be found in travis logs).

We are investigating this failures

Issue request type


[ ] Question
[ ] Enhancement
[X] Bug

CLOSED mirrored bug

All 5 comments

cc @ARMmbed/mbed-os-test @ARMmbed/mbed-os-maintainers

From the rabitmq website, they updated their keys 2 days ago. This should explain the failures

Quote from their webpage (http://www.rabbitmq.com/news.html):

On December 1st, 2018 (GMT) all repositories under the RabbitMQ account on PackageCloud will be switched to use the new signing keys. RabbitMQ users who install packages from PackageCloud must import the new signing keys before the migration. The recommended way of doing that is by re-running PackageCloud setup scripts (RabbitMQ, Erlang). Signing keys can be downloaded and imported directly as well (RabbitMQ, Erlang). If the new keys are not imported, package installation will start failing with a signature verification error.

Restarting all referenced PR here, should be green and can be closed 馃檹

Build are once again functional.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DuyTrandeLion picture DuyTrandeLion  路  3Comments

chrissnow picture chrissnow  路  4Comments

ashok-rao picture ashok-rao  路  4Comments

MarceloSalazar picture MarceloSalazar  路  3Comments

bcostm picture bcostm  路  4Comments