Makara & Remote Execution

I'm currently hitting an issue which is causing Foreman to fail to boot up,
this is occuring on Foreman 1.15.2 when installing Foremn Remote Execution.
Error seen states;

LoadError: cannot load such file – sequel/adapters/makara_postgresql (Sequel::AdapterNotFound)

I'm using Makara as a AR DB Adapter, database.yml seen here with settings
removed;

production:
adapter: 'makara_postgresql'
database: foreman
username: foreman
password: XXXXX
pool: 5
makara:
blacklist_duration: 5
master_ttl: 5
master_strategy: round_robin
sticky: true

connections:
  - role: master
    host: host1
  - role: slave
    host: host2

Having had a chat in IRC, it seems that Dynflow, called by foreman-tasks uses Sequel as it's ORM, which seems to be overwriting the default of AR, this is causing Foreman to fail completely when booting as there's no associated adapter in Sequel for Makara.

Does anyone have any ideas how to solve this, or how best to approach a workaround?

Thanks alot

Hi Iain,

I've never used makara on my own, but this change could help [1].
Please note, that in Foreman 1.15,
the file you need to change is actually here [2]

Let me know, if that helped.

[1] - https://github.com/Dynflow/dynflow/pull/257
[2] - https://github.com/theforeman/foreman-tasks/blob/0.9.x/lib/foreman_tasks/dynflow/configuration.rb#L118

– Ivan

··· On Thu, Nov 2, 2017 at 4:28 PM, Iain Walmsley wrote: > I'm currently hitting an issue which is causing Foreman to fail to boot up, > this is occuring on Foreman 1.15.2 when installing Foremn Remote Execution. > Error seen states; > > LoadError: cannot load such file -- sequel/adapters/makara_postgresql > (Sequel::AdapterNotFound) > > > I'm using Makara as a AR DB Adapter, database.yml seen here with settings > removed; > > production: > adapter: 'makara_postgresql' > database: foreman > username: foreman > password: XXXXX > pool: 5 > makara: > blacklist_duration: 5 > master_ttl: 5 > master_strategy: round_robin > sticky: true > > connections: > - role: master > host: host1 > - role: slave > host: host2 > > Having had a chat in IRC, it seems that Dynflow, called by foreman-tasks > uses Sequel as it's ORM, which seems to be overwriting the default of AR, > this is causing Foreman to fail completely when booting as there's no > associated adapter in Sequel for Makara. > > Does anyone have any ideas how to solve this, or how best to approach a > workaround? > > Thanks alot > > > > > -- > 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 https://groups.google.com/group/foreman-users. > For more options, visit https://groups.google.com/d/optout.