If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

seamonkeyproject.org's website update cron messages warning about hg.mozilla.org fingerprint

VERIFIED FIXED

Status

Infrastructure & Operations
WebOps: Other
VERIFIED FIXED
8 months ago
8 months ago

People

(Reporter: ewong, Unassigned)

Tracking

Details

(Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4183])

(Reporter)

Description

8 months ago
Post-holiday, the cron job that does the website update is now sending
messages to seamonkey-release@mo re: 

warning: hg.mozilla.org certificate with fingerprint 73:7f:ef:ab:68:0f:49:3f:88:91:f0:b7:06:69:fd:8f:f2:55:c9:56 not verified (check hostfingerprints or web.cacerts config setting)

I believe that host needs to have its fingerprints updated?  

Callek, who do I ask, as I'm not even sure which host this is on?
(Reporter)

Updated

8 months ago
Flags: needinfo?(bugspam.Callek)
(Reporter)

Updated

8 months ago
Summary: cron messages warning about hg.mozilla.org fingerprint → seamonkeyproject.org's website update cron messages warning about hg.mozilla.org fingerprint
What's the hostname in the full headers of the cronmail?
(Reporter)

Comment 2

8 months ago
it's from root@staticadm
(Reporter)

Updated

8 months ago
Assignee: nobody → server-ops-webops
Component: www.seamonkey-project.org → WebOps: Other
Product: Websites → Infrastructure & Operations
QA Contact: smani
(Reporter)

Updated

8 months ago
Flags: needinfo?(bugspam.Callek)

Updated

8 months ago
Whiteboard: [kanban:https://webops.kanbanize.com/ctrl_board/2/4183]
This was fallout from the http->https redirect on hg.m.o, and was tempfixed by adding:

[hostfingerprints]
hg.mozilla.org = 73:7F:EF:AB:68:0F:49:3F:88:91:F0:B7:06:69:FD:8F:F2:55:C9:56

to the end of staticadm:/data/static/build/seamonkeyproject-org/.hg/hgrc

While I was in there, I also updated the default pull path to https:

[paths]
default = http://hg.mozilla.org/SeaMonkey/seamonkey-project-org

So that's one less thing using non-HTTPS HG, hooray.

:ewong, this should now be resolved, and silent again. Please reopen if the messages continue to arrive after ~1hr from now (or less).
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → FIXED
See Also: → bug 450645
(Reporter)

Comment 4

8 months ago
(In reply to Richard Soderberg [:atoll] from comment #3)
> This was fallout from the http->https redirect on hg.m.o, and was tempfixed
> by adding:
> 
> [hostfingerprints]
> hg.mozilla.org = 73:7F:EF:AB:68:0F:49:3F:88:91:F0:B7:06:69:FD:8F:F2:55:C9:56
> 
> to the end of staticadm:/data/static/build/seamonkeyproject-org/.hg/hgrc
> 
> While I was in there, I also updated the default pull path to https:
> 
> [paths]
> default = http://hg.mozilla.org/SeaMonkey/seamonkey-project-org
> 
> So that's one less thing using non-HTTPS HG, hooray.
> 
> :ewong, this should now be resolved, and silent again. Please reopen if the
> messages continue to arrive after ~1hr from now (or less).

Thanks :atoll!  Confirmed fixed as I'm not receiving anything from cron now.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.