Failed gitlab-runner update. "The following signatures couldn't be verified"

Failed to fetch https://packages.gitlab.com/runner/gitlab-runner/debian/dists/stretch/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F

We need find and install new key 
# apt-get update
...
Get:8 https://packages.gitlab.com/runner/gitlab-runner/debian stretch InRelease [23.4 kB]
Err:8 https://packages.gitlab.com/runner/gitlab-runner/debian stretch InRelease
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F
...
Fetched 23.4 kB in 4s (4,794 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.gitlab.com/runner/gitlab-runner/debian stretch InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F
W: Failed to fetch https://packages.gitlab.com/runner/gitlab-runner/debian/dists/stretch/InRelease  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 3F01618A51312F3F
W: Some index files failed to download. They have been ignored, or old ones used instead.
Keys stored at keyserver.ubuntu.com. Just pass 3F01618A51312F3F to --recv-keys and that all. 
# apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
Executing: /tmp/apt-key-gpghome.KMLfZ7U2tz/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
gpg: key 3F01618A51312F3F: public key "GitLab B.V. (package repository signing key) " imported
gpg: Total number processed: 1
gpg:               imported: 1

Comments

  1. Rico70Monday, April 13, 2020 5:46:00 PM

    Nope.

    # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
    Executing: /tmp/apt-key-gpghome.CPlL2UxgMW/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
    gpg: key 3F01618A51312F3F: "GitLab B.V. (package repository signing key) " not changed
    gpg: Total number processed: 1
    gpg: unchanged: 1

    ReplyDelete
  2. UnknownWednesday, March 23, 2022 8:06:00 PM

    One more time...

    Error

    W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.gitlab.com/runner/gitlab-runner/debian stretch InRelease: The following signatures were invalid: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key)
    W: Failed to fetch https://packages.gitlab.com/runner/gitlab-runner/debian/dists/stretch/InRelease The following signatures were invalid: EXPKEYSIG 3F01618A51312F3F GitLab B.V. (package repository signing key)
    W: Some index files failed to download. They have been ignored, or old ones used instead.

    Fix

    # apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
    Executing: /tmp/apt-key-gpghome.vwgOh8kKC1/gpg.1.sh --keyserver keyserver.ubuntu.com --recv-keys 3F01618A51312F3F
    gpg: key 3F01618A51312F3F: "GitLab B.V. (package repository signing key) " 2 new signatures
    gpg: Total number processed: 1
    gpg: new signatures: 2

    Done

    # apt-get update
    ...
    Get:9 https://packages.gitlab.com/runner/gitlab-runner/debian stretch InRelease [23.5 kB]
    Ign:11 https://packages.gitlab.com/runner/gitlab-runner/debian stretch/main amd64 Packages
    Get:11 https://packages.gitlab.com/runner/gitlab-runner/debian stretch/main amd64 Packages [18.6 kB]
    Fetched 86.9 kB in 1s (73.6 kB/s)
    Reading package lists... Done

    ReplyDelete

Post a Comment

Popular posts from this blog

FreeRadius and Google Workspace LDAP

This is the first time when I used FreeRadius, this program reminds me of Postfix, I mean similar complicated and powerful tool. Only one big difference - very bad documentation and not enough examples. In the maillists a lot of questions without answers from FreeRadius guru. Here I provided examples of how I solved some problems or where I took too much time…
Read more

pssh (parallel-ssh) problems on Debian 10 with Python 3.7

Python reminds me of PHP many years ago with totally incompatible versioning on one server. Do you need another version? The best way - new servers, because any update or installation can break all global environments. Half a year after “Sunsetting Python 2” but main distributions continue to push python2 during installation and it’s a big challenge not to replace the default version after some update or installing a new package.
Read more