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.
Need to pin: pypy-2.2.1-moz0.x86_6 pypy-libs-2.2.1-moz0.x86_64
on host: etl1.bugs.scl3.mozilla.com
The current pypy packages are the correct version: [email@example.com ~]$ 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
Created attachment 8847141 [details] [diff] [review] bug1343566_pin-pypy-for-etl.patch
Attachment #8847141 - Flags: review?(klibby)
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.
Attachment #8847141 - Flags: review?(klibby) → review+
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.
Created attachment 8848198 [details] [diff] [review] 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): [firstname.lastname@example.org ~]$ 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
Attachment #8848198 - Flags: checked-in+
Status: NEW → RESOLVED
Last Resolved: 10 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.