apt-get update consistently fails on proxxy1.srv.releng.scl3.mozilla.com

RESOLVED FIXED

Status

Infrastructure & Operations
RelOps: Puppet
RESOLVED FIXED
3 years ago
3 years ago

People

(Reporter: arr, Assigned: dividehex)

Tracking

Details

Attachments

(1 attachment)

(Reporter)

Description

3 years ago
We get this message daily when apt-get update runs:

Puppet (err): /usr/bin/apt-get update returned 100 instead of one of [0]
/Stage[packagesetup]/Packages::Setup/Exec[apt-get-update-daily]/returns (err): change from notrun to 0 failed: /usr/bin/apt-get update returned 100 instead of one of [0]

In order to diagnose, we should add this to the exec statements:

logoutput => on_failure

Searching google finds a number of hits for issues with dpkg and /sbin not being in the path, but I'm not 100% certain that's what's biting us here.
(Reporter)

Comment 1

3 years ago
Created attachment 8605836 [details] [diff] [review]
apt-get-error.diff
Attachment #8605836 - Flags: review?(dustin)
Attachment #8605836 - Flags: review?(dustin) → review+
The error is

W: GPG error: https://puppetagain-apt.pvt.build.mozilla.org trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 00A6F0A3C300EE8C
W: GPG error: https://puppetagain-apt.pvt.build.mozilla.org trusty Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 1054B7A24BD6EC30
W: Failed to fetch https://puppetagain-apt.pvt.build.mozilla.org/repos/apt/releng-updates/dists/trusty-updates/all/binary-amd64/Packages  HttpError404
W: Failed to fetch https://puppetagain-apt.pvt.build.mozilla.org/repos/apt/releng-updates/dists/trusty-updates/all/binary-i386/Packages  HttpError404
E: Some index files failed to download. They have been ignored, or old ones used instead.

I think the 404's are the error, and that the GPG's are truly warnings (don't believe the "E" and "W" - apt-get is truly crappy stuff)
(Reporter)

Comment 3

3 years ago
Ah, that's a pretty straightforward problem, then.
:dividehex, I assume that /data/repos/apt/releng-updates/dists/tryusty-updates should exist and it was an oversight that it wasn't set up. Can you add this to the list of thigns to do for 14.04?
Assignee: arich → jwatkins
Flags: needinfo?(jwatkins)
(Assignee)

Comment 4

3 years ago
Simple fix. I updated the update.sh script to include trusty.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Flags: needinfo?(jwatkins)
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.