Closed Bug 922750 Opened 11 years ago Closed 11 years ago

B2G builds failing with | gpg: Can't check signature: No public key | error: could not verify the tag 'v1.12.4' | fatal: repo init failed; run without --quiet to see why

Categories

(Release Engineering :: General, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: RyanVM, Assigned: catlee)

References

Details

+++ This bug was initially created as a clone of Bug #920312 +++ This is a different issue than bug 920312. (In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #34) > https://tbpl.mozilla.org/php/getParsedLog.php?id=28621209&tree=Mozilla- > Inbound (In reply to Chris AtLee [:catlee] from comment #35) > (In reply to Ryan VanderMeulen [:RyanVM UTC-4] from comment #34) > > https://tbpl.mozilla.org/php/getParsedLog.php?id=28621209&tree=Mozilla- > > Inbound > > That's a different problem: > 10:06:34 INFO - Copy/paste: > /builds/slave/b2g_m-in_emulator-jb-d_dep-000/build/repo init --repo-url > https://git.mozilla.org/external/google/gerrit/git-repo.git -q -u > /builds/slave/b2g_m-in_emulator-jb-d_dep-000/build/tmp_manifest -m > generic.xml -b master > 10:06:38 INFO - object e76efdd7b342577c40aa271fa5ded9d66a783a9b > 10:06:38 INFO - type commit > 10:06:38 INFO - tag v1.12.4 > 10:06:38 INFO - tagger Conley Owens <cco3@android.com> 1380645867 -0700 > 10:06:38 INFO - repo 1.12.4 > 10:06:38 INFO - gpg: Signature made Tue 01 Oct 2013 09:44:27 AM PDT > using RSA key ID 692B382C > 10:06:38 INFO - gpg: Can't check signature: No public key > 10:06:38 INFO - error: could not verify the tag 'v1.12.4' > 10:06:38 INFO - fatal: repo init failed; run without --quiet to see why > 10:08:05 INFO - Traceback (most recent call last): > 10:08:05 INFO - File > "/builds/slave/b2g_m-in_emulator-jb-d_dep-000/build/repo", line 738, in > <module> > 10:08:05 INFO - main(sys.argv[1:]) > 10:08:05 INFO - File > "/builds/slave/b2g_m-in_emulator-jb-d_dep-000/build/repo", line 712, in main > 10:08:05 INFO - os.rmdir(repodir) > 10:08:05 INFO - OSError: [Errno 20] Not a directory: '.repo' > > This is caused by upstream changes to the repo tool. I'm trying to figure > out a way to handle this, as this also bit us last week. (In reply to Gregory Szorc [:gps] from comment #36) > Git supports signing commits and tags with GPG. It sounds like the public > key of the signer of that v1.12.4 tag can't be found. I'm not sure if > repo/git is smart enough to import GPG keys from public keyservers or if you > need to do it beforehand. I'm also not sure if there is a way to have repo > not verify signatures. > > It looks like the public key for this person is on a public server and can > be found at > http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x19269455338871A4. > > Perhaps this is a firewall issue? If the repo clients can't talk to the > public key servers, they obviously can't import public keys.
I don't think this a firewall issue. This also fails for me on my local machine.
Summary: B2G builds failing with | error.GitError: manifests rev-list (u'^d3a898d0ef4b0115c579a095347ce6a9498430ff', 'HEAD', '--'): fatal: bad object HEAD → B2G builds failing with | gpg: Can't check signature: No public key | error: could not verify the tag 'v1.12.4' | fatal: repo init failed; run without --quiet to see why
Upstream just released v1.12.4 a few hours ago. I've tried to reply to the thread mentioning this issue, but it's awaiting moderation. https://groups.google.com/forum/#!topic/repo-discuss/4EsDRDRK5Lk We hit this with v1.12.3 last week, and upstream quickly releases v1.12.3.1 which fixed up the problem.
Severity: critical → normal
Priority: -- → P2
Sorry, this should be in RelEng's pile-o-bugs.
Assignee: server-ops-webops → nobody
Severity: normal → critical
Component: WebOps: Source Control → General Automation
Product: Infrastructure & Operations → Release Engineering
QA Contact: nmaul → catlee
in production
Assignee: nobody → catlee
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Depends on: 1007259
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.