Closed
Bug 946872
Opened 11 years ago
Closed 10 years ago
Upgrade to puppet-3.4.2 / Facter-1.7.5
Categories
(Infrastructure & Operations :: RelOps: Puppet, task)
Infrastructure & Operations
RelOps: Puppet
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dustin, Assigned: dustin)
References
Details
Attachments
(3 files)
3.03 KB,
patch
|
Callek
:
review+
|
Details | Diff | Splinter Review |
1.45 KB,
patch
|
Callek
:
review+
dustin
:
checked-in+
|
Details | Diff | Splinter Review |
2.57 KB,
patch
|
Callek
:
review+
dustin
:
checked-in+
|
Details | Diff | Splinter Review |
This upgrade should also include the fix for http://projects.puppetlabs.com/issues/22107 on Mavericks, meaning custom-built DMGs.
Assignee | ||
Comment 2•11 years ago
|
||
The custom-built DMG should also contain the patch for the recent ruby vulns, whatever they may be when I get around to this (collect them all!!)
Assignee | ||
Updated•11 years ago
|
Summary: Upgrade to puppet-3.4.0 → Upgrade to puppet-3.4.1
Assignee | ||
Comment 4•10 years ago
|
||
The combination of Puppet-3.4.2 and Facter-1.7.5 should be mavericky-compatible (but needs testing!)
Summary: Upgrade to puppet-3.4.1 → Upgrade to puppet-3.4.3 / Facter-1.7.5
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Comment 5•10 years ago
|
||
I'll find a way to test this out in relabs, once we have more of the relabs systems up and running.
Assignee | ||
Comment 6•10 years ago
|
||
OK, this is running in my environment in relabs. I'll need to spin up some OS X and Ubuntu systems to check those out, then I can ship it. File syncing from moco to relabs is disabled temporarily.
Assignee | ||
Updated•10 years ago
|
Summary: Upgrade to puppet-3.4.3 / Facter-1.7.5 → Upgrade to puppet-3.4.2 / Facter-1.7.5
Assignee | ||
Comment 7•10 years ago
|
||
Hm, those minis seem to have corrupt filesystems..
Assignee | ||
Comment 8•10 years ago
|
||
Works fine on Mountain Lion.
Assignee | ||
Comment 9•10 years ago
|
||
The upgrade was a little rocky on Mavericks - some ruby errors about modules not existing. I assume those are from require's that occur after the upgrade of puppet, and thus don't find the right source code. That run of puppet failed, but the next one succeeded.
Assignee | ||
Comment 10•10 years ago
|
||
..and verified on Ubuntu as well. I think we're ready to go here! We can do one operating system at a time, starting with CentOS (so the masters get updated).
Assignee | ||
Comment 11•10 years ago
|
||
Attachment #8386175 -
Flags: review?(bugspam.Callek)
Assignee | ||
Comment 12•10 years ago
|
||
Oh, I'll only bump the yum repoflag; ignore the other hunk.
Comment 13•10 years ago
|
||
Comment on attachment 8386175 [details] [diff] [review] bug946872.patch Review of attachment 8386175 [details] [diff] [review]: ----------------------------------------------------------------- r+ without the deb repoflag change as discussed ::: modules/packages/manifests/puppet.pp @@ +15,5 @@ > + $old_facter_version = "1.7.1" > + $new_facter_version = "1.7.5" > + $facter_dmg_version = "${old_facter_version}" > + $facter_rpm_version = "${new_facter_version}-1.el6" > + $facter_deb_version = "${old_facter_version}-1puppetlabs1" nit: drop "new_" from these vars, not worth the confusion once we drop "old_" If you have a compelling reason to leave as-is it's acceptable though
Attachment #8386175 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Comment 14•10 years ago
|
||
I'm going to keep new until they're all new, then drop it.
Assignee | ||
Comment 15•10 years ago
|
||
Notice: /Stage[main]/Packages::Puppet/Package[facter]/ensure: ensure changed '1.7.1-1.el6' to '1.7.5-1.el6' Notice: /Stage[main]/Packages::Puppet/Package[puppet]/ensure: ensure changed '3.2.2-1.el6' to '3.4.2-1.el6' Notice: Finished catalog run in 26.62 seconds re-run works fine. Things went a little less well on the puppet masters. I think what happened is this: the upgrade of puppet caused an upgrade of puppet-server as well, but to the latest version in the repo (3.4.3). The later attempt to "upgrade" puppet-server to 3.4.2 failed because by then it was a downgrade. I manually ran 'yum downgrade' on the puppet masters (along with a manual 'service httpd restart') and this seemed to fix it. I emailed the list.
Assignee | ||
Comment 16•10 years ago
|
||
Attachment #8386842 -
Flags: review?(bugspam.Callek)
Updated•10 years ago
|
Attachment #8386842 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Comment 17•10 years ago
|
||
Ubuntu repos are sync'd, ready to roll on Monday.
Assignee | ||
Comment 18•10 years ago
|
||
Comment on attachment 8386842 [details] [diff] [review] bug946872-p1.patch [root@talos-linux64-ix-011.test.releng.scl3.mozilla.com ~]# puppet --version 3.4.2 looks fine from here
Attachment #8386842 -
Flags: checked-in+
Assignee | ||
Comment 19•10 years ago
|
||
..and finally, OS X.
Attachment #8389291 -
Flags: review?(bugspam.Callek)
Comment 20•10 years ago
|
||
Comment on attachment 8389291 [details] [diff] [review] bug946872-p2.patch Review of attachment 8389291 [details] [diff] [review]: ----------------------------------------------------------------- feel free to deploy this today, just ping in #releng so I know
Attachment #8389291 -
Flags: review?(bugspam.Callek) → review+
Assignee | ||
Updated•10 years ago
|
Attachment #8389291 -
Flags: checked-in+
Assignee | ||
Comment 21•10 years ago
|
||
I'm not seeing any errors, so I'm going to cautiously call this fixed. Yay!
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 22•10 years ago
|
||
Worth noting here: this facter upgrade is to the newest version, but it still doesn't get the ec2_* facts.
You need to log in
before you can comment on or make changes to this bug.
Description
•