Is it possible to upgrade to 1.4 directly from 1.2.2?

Support
1

Greetings,
I had been preparing to upgrade from 1.2.2 to 1.3 before having to take
an extended medical leave. Now that I'm back in action, I'm curious if
there's a safe RPM upgrade process to jump from 1.2.2 to 1.4 or if I should
use yum version lock to lock the foreman package at 1.3.latest and
basically do two upgrades?

Thanks for your suggestions!

2

Sean

I've done the same upgrade on one of my dev envs without any major
issues…
Must remember to updates the nodes and reports files, and I also hit a
package depencendy issue on CentOS due to an installed package that was
no-longer required… rubygem-net-ldap rings a bell…

If you can clone or snapshot your Foreman server, then go for it :slight_smile:

Cheers
Gav

··· On Tuesday, 4 February 2014 14:29:01 UTC, Sean Alderman wrote: > > Greetings, > I had been preparing to upgrade from 1.2.2 to 1.3 before having to take > an extended medical leave. Now that I'm back in action, I'm curious if > there's a safe RPM upgrade process to jump from 1.2.2 to 1.4 or if I should > use yum version lock to lock the foreman package at 1.3.latest and > basically do two upgrades? > > Thanks for your suggestions! >
3

Gavin,
Thanks for your reply. I had already gotten into the 1.3 upgrade before
I saw your reply. After tinkering with the foreman.rb, I updated node.rb
and got lots of agent errors aftewards. The only term I immediately recall
from the error message was "fixnum". Anyway, I restored the original
node.rb and all seems fine.

After that I went through and upgraded puppet/puppetmaster from 2.7 to
3.3 and proceded to upgrade foreman again to 1.4.

All seems to be well.

··· On Tue, Feb 4, 2014 at 10:52 AM, Gavin Williams wrote:

Sean

I’ve done the same upgrade on one of my dev envs without any major
issues…
Must remember to updates the nodes and reports files, and I also hit a
package depencendy issue on CentOS due to an installed package that was
no-longer required… rubygem-net-ldap rings a bell…

If you can clone or snapshot your Foreman server, then go for it :slight_smile:

Cheers
Gav

On Tuesday, 4 February 2014 14:29:01 UTC, Sean Alderman wrote:

Greetings,
I had been preparing to upgrade from 1.2.2 to 1.3 before having to take
an extended medical leave. Now that I’m back in action, I’m curious if
there’s a safe RPM upgrade process to jump from 1.2.2 to 1.4 or if I should
use yum version lock to lock the foreman package at 1.3.latest and
basically do two upgrades?

Thanks for your suggestions!

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/groups/opt_out.

–
Sean M. Alderman
Senior Engineer, UDit Systems Integration and Engineering
University of Dayton
salderman1@udayton.edu

“We are not some casual and meaningless product of evolution. Each of us
is the result of a thought of God. Each of us is willed. Each of us is
loved. Each of us is necessary.” - BXVI