1343566 - Pin bmo es etl pypy in puppet

Status: RESOLVED FIXED

(Developer Services :: General, task)

Description

[:dhouse]

We need to keep the custom pypy build on the bmo elasticsearch ETC batch/script server. Pinning it in puppet would prevent it from being "upgraded" to an older version.

Comment 1

[:dhouse]

Need to pin:
pypy-2.2.1-moz0.x86_6
pypy-libs-2.2.1-moz0.x86_64

Comment 2

[:dhouse]

on host:
etl1.bugs.scl3.mozilla.com

Comment 3

[:dhouse]

The current pypy packages are the correct version:
[[e-mail]3 ~]$ rpm -q pypy pypy-devel pypy-libs
pypy-2.2.1-moz0.x86_64
pypy-devel-2.2.1-moz0.x86_64
pypy-libs-2.2.1-moz0.x86_64

Comment 4

[:dhouse]

Attachment: bug1343566_pin-pypy-for-etl.patch

Comment 5

[Kendall Libby [:fubar] (he/him)]

Comment on attachment 8847141 [details] [diff] [review]
bug1343566_pin-pypy-for-etl.patch

Review of attachment 8847141 [details] [diff] [review]:
-----------------------------------------------------------------

Using ensure on the package version won't prevent us from accidentally upgrading pypy, it will just downgrade it on the next puppet run. That's probably acceptable on this host; if the cron job fails for 30-60 minutes it's unlikely that anyone will notice. 

If you want to go the extra step, util::lock_package will prevent us from upgrading.

Comment 6

[:dhouse]

Thank you for pointing that out! I'll add the lock_package setting so that it doesn't get upgraded. I don't want for a downgrade to be needed since there could be problems/failures with that.

Comment 7

[:dhouse]

Attachment: bug1343566_pin-pypy-for-bmo-es-etl.patch

Confirmed works when running against etl (versionlock was installed automatically by puppet once the util:lock_version was used):
[[e-mail]3 ~]$ sudo yum versionlock
Loaded plugins: rhnplugin, security, versionlock
This system is receiving updates from RHN Classic or RHN Satellite.
0:pypy-2.2.1-moz0.*
0:pypy-devel-2.2.1-moz0.*
0:pypy-libs-2.2.1-moz0.*
versionlock list done