If you feel this is an error with Foreman itself, please open a new issue
with Foreman ticketing system http://theforeman.org/projects/foreman/issues, You would probably need to
attach the Full trace https://lvs01ppm01.stratus.lvs.ebay.com/users/login#
and relevant log entries. NoMethodError
*undefined method find_by_lower_login' for #<Class:0x0000000879b2d0>* app/models/user.rb:263:infind_by_login’
app/models/user.rb:188:in try_to_login' app/controllers/users_controller.rb:71:inlogin’
app/models/concerns/foreman/thread_session.rb:33:in clear_thread' lib/middleware/catch_json_parse_errors.rb:9:incall’
Back https://lvs01ppm01.stratus.lvs.ebay.com/
I must be missing some package that installer does not bring in either.
Maybe some GEM or something?
> I have a problem while migrating from 1.5.3 to 1.7.1.
This is not supported, you should upgrade to 1.6 and then 1.7. But you
can always backup and at least try it if it works.
> cannot load such file – apipie/middleware/checksum_in_
> headers
You must have inocrrect version of apipie gem. Have you followed our
upgrade instructions carefully? You need to do yum upgrade foreman*
packages as well as all rubygem* packages (or ruby193-rubygem*). See the
manual chapter.
Sorry for extra post. However, the only response I've got was for this 2nd
post.
>
> > I have a problem while migrating from 1.5.3 to 1.7.1.
>
> This is not supported, you should upgrade to 1.6 and then 1.7. But you
> can always backup and at least try it if it works.
>
Hmm, I must have missed that in release nodes. Wanted to double-check, but
can't get to theforeman.org for a second day now - do you know what's going
on?
> > cannot load such file – apipie/middleware/checksum_in_
> > headers
>
> You must have inocrrect version of apipie gem. Have you followed our
> upgrade instructions carefully? You need to do yum upgrade foreman*
> packages as well as all rubygem* packages (or ruby193-rubygem*). See the
> manual chapter.
>
Below is the list of the packages and versions. I did follow the
instructions to upgrade my Foreman VM. However, the issues I'm having must
be related to the fact that I skipped the db:migrate when moving from 1.5.x
to 1.6.x, so packages were properly upgraded, but DB was not.
If you have some suggestions on handling this kind of situation, I'd love
to hear that - I really don't want to build a VM with 1.6.x just to do a
db:migrate. I will, of course, if no other possibilities exist.
Please note that foreman-debug did not seem to correctly discover a fact
that I'm running puppet and passenger under rvm with ruby 2.1.3p242, but i
don't think it has anything to do with Foreman, which uses ruby 1.9.3 from
ruby193 SCL.
By default each user will get ruby-2.1.3, so before i execute
foreman-installer, for example, I have to run "rvm use system".
Now, foreman-rake script does "su - foreman…" and runs a command within
that, so su'ing to foreman drops back to ruby-2.1.3 and thus not finding a
gem (as the paths different).
I should be able to do the above on production now and proceed further with
1.7.1.
Sometimes just laying the facts for other people to understand the
situation solves the problem
I don't recommend to use RVM/RBENV on installer-based deployments. We do
fully support several linux distros and our repos contain all the
required dependencies.
LZ
···
On Thu, Feb 05, 2015 at 12:59:23PM -0800, Konstantin Orekhov wrote:
> Actually RVM *is* at play here.
>
> By default each user will get ruby-2.1.3, so before i execute
> foreman-installer, for example, I have to run "rvm use system".
> Now, foreman-rake script does "su - foreman..." and runs a command within
> that, so su'ing to foreman drops back to ruby-2.1.3 and thus not finding a
> gem (as the paths different).
>
> I should be able to do the above on production now and proceed further with
> 1.7.1.
>
> Sometimes just laying the facts for other people to understand the
> situation solves the problem :)
