Closed
Bug 585923
Opened 15 years ago
Closed 15 years ago
puppet not returning proper OS X version on a few slaves
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: bear, Unassigned)
References
Details
(Whiteboard: [puppet])
I noticed in the puppet logs:
Aug 10 05:31:23 production-puppet puppetmasterd[19229]: No matching value for selector param '10.4.0' at /etc/puppet/manifests/base/os.pp:13 on node moz2-darwin10-slave46.build.mozilla.org
Aug 10 05:39:27 production-puppet puppetmasterd[19274]: No matching value for selector param '10.4.0' at /etc/puppet/manifests/base/os.pp:13 on node try-mac64-slave17.build.mozilla.org
It appears that facter is reporting kernel version 10.4 but the sw_vers tool is reporting 10.6.*
Only these two slaves have this problem
Reporter | ||
Updated•15 years ago
|
Whiteboard: [puppet]
Comment 1•15 years ago
|
||
Also on:
moz2-darwin10-slave45
Because a successful Puppet run now blocks starting Buildbot, these slaves aren't coming online at all.
Severity: normal → major
Summary: puppet not returning proper OS X version for two slaves → puppet not returning proper OS X version on a few slaves
Comment 2•15 years ago
|
||
Those three machines got updated to 10.6.4 to try to fix the hang in buildsymbols, so they report 10.4.0 instead of 10.2.0. They're being reimaged to 10.6.2 in bug 584933 so this will go away then.
Comment 3•15 years ago
|
||
I stopped Puppet on these machines to get rid of the log messages on the Puppet masters.
Comment 4•15 years ago
|
||
Based on comments 2,3, nothing to do here.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•