Closed
Bug 641381
Opened 15 years ago
Closed 12 years ago
Update linux ix to glibc-2.5-42, including ref image
Categories
(Infrastructure & Operations Graveyard :: CIDuty, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Unassigned)
Details
(Whiteboard: [buildslaves])
The glibc-2.5-12 that we have as stock on the linux32 ref images is known to cause buildbot masters to crash in python. catlee figured out the fix in bug 532501 comment #14, which is update to glibc-2.5-42. In particular we have been installing
glibc-2.5-42.el5_4.3.i686.rpm
glibc-common-2.5-42.el5_4.3.i386.rpm
glibc-devel-2.5-42.el5_4.3.i386.rpm
glibc-headers-2.5-42.el5_4.3.i386.rpm
There is a copy of those in various places, eg buildbot-master1:~root/. Note that we've left glibc-debuginfo and glibc-debuginfo-common unchanged.
My primary motivation is to get this into the linux ref images, particularly for ix, so that we don't spin up more masters and retrospectively apply this fix. But it's possible, but unlikely, that this could be causing crashes on builders too, and we could consider pushing this out globally, eg using Puppet. That would be better than some build slaves having new glibc and others an old one. Comments ?
| Assignee | ||
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
Comment 1•12 years ago
|
||
Found in triage.
Is this still an issue? If yes, should this be morphed into a puppet bug?
Component: Other → Platform Support
| Reporter | ||
Comment 2•12 years ago
|
||
Fixed by moving to 64bit Centos 6 for masters:
$ rpm -qa | grep glibc
glibc-devel-2.12-1.47.el6_2.5.x86_64
glibc-common-2.12-1.47.el6_2.5.x86_64
glibc-headers-2.12-1.47.el6_2.5.x86_64
glibc-2.12-1.47.el6_2.5.x86_64
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
| Assignee | ||
Updated•8 years ago
|
Component: Platform Support → Buildduty
Product: Release Engineering → Infrastructure & Operations
Updated•6 years ago
|
Product: Infrastructure & Operations → Infrastructure & Operations Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•