FYI for anyone trying to do a full install from our yum repo (even
though the solr puppet stuff isn't there yet), maybe this will make
things a _little_ simpler for a day or two until we get this sorted.
Details below, but basically there is an issue with rsolr 1.0.0 not
being compatible with the newest sunspot, so everyone should stick with
using:
rake gems:install
for now. We'll update the list as soon as this is resolved. Vit is
going to check in with upstream for fix options, otherwise we'll roll
the rpm back to 0.12.1.
-------- Forwarded Message --------
From: Vít Ondruch <vondruch(a)redhat.com>
To: Mohammed Morsi <mmorsi(a)redhat.com>
Cc: Jason Guiditta <jguiditt(a)redhat.com>, Mike Orazi
<morazi(a)redhat.com>, athomas(a)redhat.com
Subject: Re: rsolr / sunspot compatibility issues
Date: Tue, 25 Jan 2011 17:27:01 +0100
Dne 24.1.2011 19:25, Mohammed Morsi napsal(a):
* it seems sunspot 1.2.1 isn't compatible with rsolr 1.0.0, trying to
use it in the context of aeolus (eg running 'rake sunspot:redindex' in
the aeolus conductor project root) results in the following error:
uninitialized constant RSolr::Message
Looking at the rsolr git repo, RSolr::Message (previously defined in
lib/rsolr/message.rb) was removed with commit
54e8100302ef6e27015a05442cd90bcb57ab961f which occured on 06/17/10,
after the 0.12.1 release was cut on 02/10/10 but before the 1.0.0
release on 01/05/11 (a few weeks ago).
-Mo
I cannot reproduce your way, however djohnson found another:
[vondruch@dhcp-25-1 src (master *)]$ rm db/development.sqlite3
[vondruch@dhcp-25-1 src (master *)]$ rake db:migrate
(in /home/vondruch/projects/conductor/src)
== CreateSessions: migrating
=================================================
-- create_table(:sessions)
-> 0.0014s
-- add_index(:sessions, :session_id)
-> 0.0004s
-- add_index(:sessions, :updated_at)
-> 0.0006s
== CreateSessions: migrated (0.0026s)
========================================
...
== CreateDeployables: migrating
==============================================
-- create_table(:deployables)
-> 0.0014s
== CreateDeployables: migrated (0.0015s)
=====================================
[vondruch@dhcp-25-1 src (master *)]$ rake db:seed
(in /home/vondruch/projects/conductor/src)
rake aborted!
uninitialized constant RSolr::Message
(See full trace by running task with --trace)
[vondruch@dhcp-25-1 src (master *)]$ rake db:seed
(in /home/vondruch/projects/conductor/src)
rake aborted!
Validation failed: {{errors}}
(See full trace by running task with --trace)
[vondruch@dhcp-25-1 src (master *)]$
So as you see, it can be reproduced when you establish fresh db and runs
"rake db:seed". There is already different error second time.
I will take a look into this issue tomorrow. I will see if upstream has
some fix or we should revert rsolr, but I hope the upstream is the way.
Vit