hostnames incorrect on some old masters

RESOLVED WORKSFORME

Status

Release Engineering
General
P2
normal
RESOLVED WORKSFORME
7 years ago
5 years ago

People

(Reporter: arr, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [buildmasters])

(Reporter)

Description

7 years ago
In adding the ganglia checks to the buildbot masters, I have discovered the following masters whose hostname does not match their A/PTR record:

buildbot-master3
production-mobile-master
staging-master
staging-mobile-master
test-master1

This means that the ganglia checks will be non-functional for them.  After dicussion on irc, dustin suggested I open up a bug to see if we can get the hostnames on these hosts changed to the correct FQDN so that the checks will function.

The other masters (both old and new) have the correct FQDN.
By "hostname" Amy means the kernel's hostname (from uname).

This is used by Buildbot as part of the master_name, which appears in the buildrequests table.  It's fetched via uname().

I think that changing this would be possible, but it would require a more-or-less-simultaneous change to production-masters.json, an UPDATE to the buildrequests table, a 'hostname' invocation on the master itself, and a restart of the master instance (or some fun with manhole).

Is it worth it, since these are "old" masters?

Updated

7 years ago
Priority: -- → P2
Whiteboard: [slaveduty]
how is this a slaveduty issue?  These are masters..
Whiteboard: [slaveduty]

Comment 3

7 years ago
/me distracts dustin with a shiny object
/me edits
/me does the "nothing to see here" whistle
Whiteboard: [buildmasters]
(Reporter)

Comment 4

7 years ago
Interestingly, these checks seem to have corrected themselves at this point.  I'm not sure how or why, but I guess you can WONTFIX this if you like.
yay?
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
(Assignee)

Updated

5 years ago
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.