734349 - install libasound 1.0.14 on linux build and test machines

Status: RESOLVED FIXED

(Infrastructure & Operations Graveyard :: CIDuty, task)

Description

[[e-mail] (:bhearsum)]

For bug 697754. Do we need it installed on test machines, too?

Comment 1

[[e-mail] (:bhearsum)]

Turns out this package is one of (or more likely, all of) the following on CentOS, which explains why I couldn't find libasound RPMs ;)
alsa-lib-devel
alsa-utils
alsa-lib

Comment 2

[[e-mail] (:bhearsum)]

OK, I found binary RPMs for the build machines. I've installed them on one of the machines and I'm looking to run a set of tests to see what kind of failures they cause, if any.

Comment 3

[[e-mail] (:bhearsum)]

Per IRC with rjesup, we'll need these packages on both build and test machines, but build machines are the priority. There aren't any tests to fail yet, so the test machines will be OK as they are for now.

Comment 4

[[e-mail] (:bhearsum)]

Attachment: puppet manifests for centos build machines

Because of releases we can't land this until next week. To land, we need to copy all of the alsa packages currently in /N/staging/centos5-{i386,x86_64}/build/RPMs to /N/production, scl-production-puppet, and mv-production-puppet - and then land the manifests and update the masters.

Still to do in this bug after that: fedora updates.

Comment 5

[[e-mail] (:bhearsum)]

Comment on attachment 604477 [details] [diff] [review]
puppet manifests for centos build machines

(In reply to Ben Hearsum [:bhearsum] from comment #4)
> Created attachment 604477 [details] [diff] [review]
> puppet manifests for centos build machines
> 
> Because of releases we can't land this until next week. To land, we need to
> copy all of the alsa packages currently in
> /N/staging/centos5-{i386,x86_64}/build/RPMs to /N/production,
> scl-production-puppet, and mv-production-puppet

# root@production-puppet
rsync -av --include=centos* --include=build --include=RPMs --include=alsa*.rpm --exclude=* /N/staging/ /N/production/
rsync -av --include=centos* --include=build --include=RPMs --include=alsa*.rpm --exclude=* /N/production/ scl-production-puppet.build.scl1.mozilla.com:/N/production/
rsync -av --include=centos* --include=build --include=RPMs --include=alsa*.rpm --exclude=* /N/production/ mv-production-puppet.build.mtv1.mozilla.com:/N/production/

and then land the
> manifests and update the masters.

Done.

I've manually checked some slaves, too, and they're all picking up the updates fine.

Randall, it will take 10-12 hours for this update to reach all of the build machines. You can take your chances and try to push to try and hope you get one with it today, or you can wait until tomorrow to be sure.

> Still to do in this bug after that: fedora updates.

On this topic, I just checked on of the fedora machines and found that we have these packages on them (64-bit is the same with a different arch):
alsa-lib-1.0.21-3.fc12.i686
alsa-utils-1.0.21-2.fc12.i686

Given that, I think we're OK on all fronts now?

Comment 6

[Randell Jesup [:jesup] (needinfo me)]

Yes, I believe so.  If there are any issues, I'll reopen or whatever is needed.  1.0.21 for Fedora should be great.

Comment 7

[[e-mail] (:bhearsum)]

Woot, this turned out to be relatively painless.