Virtual-environments: Ubuntu 18.04 Virtual Environment: MongoDB GPG key issue

[darkwizard242]

Describe the bug
Appears that the mongodb gpg key is missing on Ubuntu 18.04 LTS virtual environment

Area for Triage:
Servers

Question, Bug, or Feature?:
Bug

Virtual environments affected

• [ ] macOS 10.15
• [ ] Ubuntu 16.04 LTS
• [x] Ubuntu 18.04 LTS
• [ ] Ubuntu 20.04 LTS
• [ ] Windows Server 2016 R2
• [ ] Windows Server 2019

Expected behavior
Clean update of repository cache using sudo apt-get update

Actual behavior
An error for mongodb repository's gpg key.

To reproduce, run sudo apt-get update on Ubuntu 18.04 LTS virtual environment.

Error:

Err:14 https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.2 Release.gpg
  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 656408E390CFB1F5

W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repo.mongodb.org/apt/ubuntu bionic/mongodb-org/4.2 Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 656408E390CFB1F5
W: Failed to fetch https://repo.mongodb.org/apt/ubuntu/dists/bionic/mongodb-org/4.2/Release.gpg  The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 656408E390CFB1F5

Temporary workaround
Adding the missing (or updated) key manually in a step within the workflow with something like the following:

steps:
- name: Adding missing key and update repository cache
  run: |
      sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 656408E390CFB1F5
      sudo apt-get update

[clhuang]

it seems to be a mistake on the mongodb side of things-- the key 656408E390CFB1F5 seems to be their 4.4 release signing key:

(from https://keyserver.ubuntu.com/pks/lookup?search=mongodb&fingerprint=on&op=index)

[miketimofeev]

Hi @darkwizard242 as @clhuang said this is MongoDB issue, we're experiencing the same issue at the moment and can't build an Ubuntu 16 or 18 image.

[darkwizard242]

@miketimofeev @clhuang - Thanks for checking up on that. Please forgive my ignorance, is there any issue with adding the key 656408E390CFB1F5 to the Ubuntu (bionic/xenial) image builds? Purely asking out of curiosity.

[miketimofeev]

@darkwizard242 actually it looks like the issue has already resolved,

  build:
    runs-on: ubuntu-18.04
    steps:
      - uses: actions/checkout@v2
      - name: check update18
        run: |
          sudo apt-get update

works just fine for me

[darkwizard242]

@miketimofeev - Awesome, I removed the temporary workaround added earlier when I noticed this issue. Doesn't persist anymore and repo cache update is clean. Thanks for your time and help :+1:

[miketimofeev]

@darkwizard242 feel free to contact us! I'm going to close the issue.
Thank you!