Install foreman plugins on RPM based installation

Support
1

Hi together,
I'm thinking about how to install foreman plugins when using a rpm based
installation.
As bundle update does not work there without an existent Gemfile.

Any ideas on how to integrate the plugins on rpms based installation?

Thanks for your help
Marc.

2

I haven't tested it yet, but I think the way to do it on the Foreman 1.2
SCL enabled installation is:

scl enable ruby193 'gem install your_foreman_plugin'
echo 'gem "your_foreman_plugin"' > ~foreman/bundler.d/your_plugin.rb
service httpd restart

If it works, we need to update the wiki I think and perhaps get plugin
README files to point to this page:

http://projects.theforeman.org/projects/foreman/wiki/How_to_Install_a_Plugin

We're using a project called bundler_ext, which should still load
rubygems that are installed using the Gemfile.in and bundler.d
directory. We no longer use bundle install/update, which makes it
generally much more reliable when working with gems packaged as RPMs (no
Gemfile.lock).

··· On 26/06/13 10:51, Marc Grimme wrote: > Hi together, > I'm thinking about how to install foreman plugins when using a rpm based > installation. > As bundle update does not work there without an existent Gemfile. > > Any ideas on how to integrate the plugins on rpms based installation?

–
Dominic Cleal
Red Hat Engineering

3

This should really work. Make sure you have all the deps tho.

What you can do is you can rename Gemfile.in to Gemfile and do

scl enable ruby193 'bundle install'

after you add your own dependencies there, but you have been warned!
Bundler will start mixing up RPM installed gems with his own and you
will end up with an unclean instance.

I'd recommend what Dominic says.

LZ

··· On Wed, Jun 26, 2013 at 11:02:01AM +0100, Dominic Cleal wrote: > On 26/06/13 10:51, Marc Grimme wrote: > > Hi together, > > I'm thinking about how to install foreman plugins when using a rpm based > > installation. > > As bundle update does not work there without an existent Gemfile. > > > > Any ideas on how to integrate the plugins on rpms based installation? > > I haven't tested it yet, but I think the way to do it on the Foreman 1.2 > SCL enabled installation is: > > scl enable ruby193 'gem install your_foreman_plugin' > echo 'gem "your_foreman_plugin"' > ~foreman/bundler.d/your_plugin.rb > service httpd restart > > If it works, we need to update the wiki I think and perhaps get plugin > README files to point to this page: > > http://projects.theforeman.org/projects/foreman/wiki/How_to_Install_a_Plugin > > We're using a project called bundler_ext, which should still load > rubygems that are installed using the Gemfile.in and bundler.d > directory. We no longer use bundle install/update, which makes it > generally much more reliable when working with gems packaged as RPMs (no > Gemfile.lock). > > -- > Dominic Cleal > Red Hat Engineering > > -- > 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. > >

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

4

Thanks for those pointers.
As I work with local plugins I believe life is easy for me. Just define the
appropriate file in bundle.d.
The other thing is as I'm using foreman1.2RC3 updated from foreman 1.1 I
think I'll also need a:
RAILS_ENV=production bundle exec rake db:migrate assets:precompile
locale:pack
Won't I?

But now I try to start rails I get the following error:
scl enable ruby193 './script/rails s --environment=production'
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in
strict_error': Gem loading error: cannot load such file -- spice/html5/rails (RuntimeError) from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:53:inrescue in rescue in block in system_require'
from
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:43:in
rescue in block in system_require' from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:inblock in system_require'
from
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
each' from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:insystem_require'
from /usr/share/foreman/config/application.rb:11:in <top (required)>' from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
require&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:53:inblock in <top (required)>'
from
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:50:in
tap&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:50:in<top (required)>'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require&#39; from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require&#39; from ./script/rails:6:in<main>'

Any ideas?

Besides: There is no direct connection to the internet from that host (only
proxy).

Thanks Marc.

··· On Wednesday, June 26, 2013 12:49:59 PM UTC+2, Dominic Cleal wrote: > > On 26/06/13 11:48, Lukas Zapletal wrote: > > This should really work. Make sure you have all the deps tho. > > > > What you can do is you can rename Gemfile.in to Gemfile and do > > > > scl enable ruby193 'bundle install' > > > > after you add your own dependencies there, but you have been warned! > > Bundler will start mixing up RPM installed gems with his own and you > > will end up with an unclean instance. > > > > I'd recommend what Dominic says. > > Ugh yeah, I wouldn't confuse things with Bundler! > > gem install will obey the dependencies listed for the plugin in its > gemspec, so hopefully that'll just work. > > -- > Dominic Cleal > Red Hat Engineering >
5

Ugh yeah, I wouldn't confuse things with Bundler!

gem install will obey the dependencies listed for the plugin in its
gemspec, so hopefully that'll just work.

··· On 26/06/13 11:48, Lukas Zapletal wrote: > This should really work. Make sure you have all the deps tho. > > What you can do is you can rename Gemfile.in to Gemfile and do > > scl enable ruby193 'bundle install' > > after you add your own dependencies there, but you have been warned! > Bundler will start mixing up RPM installed gems with his own and you > will end up with an unclean instance. > > I'd recommend what Dominic says.

–
Dominic Cleal
Red Hat Engineering

6

> Thanks for those pointers.
> As I work with local plugins I believe life is easy for me. Just define
> the appropriate file in bundle.d.
> The other thing is as I'm using foreman1.2RC3 updated from foreman 1.1 I
> think I'll also need a:
> RAILS_ENV=production bundle exec rake db:migrate assets:precompile
> locale:pack
> Won't I?

You need a db:migrate immediately after upgrading, but not after that.
The assets:precompile and locale:pack aren't needed if you're using
RPMs, we do that in the build process and so the final Foreman RPM
contains everything required to run.

> But now I try to start rails I get the following error:
> scl enable ruby193 './script/rails s --environment=production'yes,
> /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in
> `strict_error': Gem loading error: cannot load such file –
> spice/html5/rails (RuntimeError)

Odd, do you have foreman-assets installed or something?

··· On 26/06/13 14:37, Marc Grimme wrote:

–
Dominic Cleal
Red Hat Engineering

7

> > Thanks for those pointers.
> > As I work with local plugins I believe life is easy for me. Just define
> > the appropriate file in bundle.d.
> > The other thing is as I'm using foreman1.2RC3 updated from foreman 1.1 I
> > think I'll also need a:
> > RAILS_ENV=production bundle exec rake db:migrate assets:precompile
> > locale:pack
> > Won't I?
>
> You need a db:migrate immediately after upgrading, but not after that.
> The assets:precompile and locale:pack aren't needed if you're using
> RPMs, we do that in the build process and so the final Foreman RPM
> contains everything required to run.
>
Got it thanks.

>
> > But now I try to start rails I get the following error:
> > scl enable ruby193 './script/rails s --environment=production'yes,
> >
> /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in
>
> > strict_error&#39;: Gem loading error: cannot load such file -- &gt; &gt; spice/html5/rails (RuntimeError) &gt; &gt; Odd, do you have foreman-assets installed or something? &gt; No I didn&#39;t. But after doing so I&#39;ll end up here: bash-4.1$ scl enable ruby193 &#39;./script/rails s --environment=production&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire': iconv will be deprecated in the future, use String#encode
instead.
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in
strict_error&#39;: Gem loading error: cannot load such file -- rack/openid (RuntimeError) from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:53:inrescue in rescue in block in system_require'
from
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:43:in
rescue in block in system_require&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:inblock in system_require'
from
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
each&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:insystem_require'
from /usr/share/foreman/config/application.rb:11:in &lt;top (required)&gt;&#39; from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
require&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:53:inblock in <top (required)>'
from
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:50:in
tap&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/commands.rb:50:in<top (required)>'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in
require&#39; from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:inrescue in require'
from
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:35:in
require&#39; from ./script/rails:6:in<main>'

Didn't find any rpm suiting the required gem.

What am I missing?

Thanks Marc.

··· On Thursday, June 27, 2013 10:17:52 AM UTC+2, Dominic Cleal wrote: > On 26/06/13 14:37, Marc Grimme wrote:
8

Bundler_ext tries to require gemname, then if there is a dash in the
name it also tries with /.

Try to use :require => in the Gemfile to specify correct require
statement. Bundler_ext respects that.

LZ

··· On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote: > `strict_error': Gem loading error: cannot load such file -- rack/openid

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

9

Thanks for the input.
I finally got it running.
I need to change/remove the following files from the original of the rpm
provided ones:
Removed:
* rm bundler.d/{development.rb,mysql2.rb,mysql.rb,ovirt.rb,test.rb}
Remark: In this environment I don't need mysql and ovirt so I removed it.
Means I cannot report on functionality.

Changed:

  • bundler.d/console.rb:
    --------------------X8-------------------------
    — bundler.d/console.rb.orig 2013-06-28 08:36:45.999936152 +0000
    +++ bundler.d/console.rb 2013-06-28 08:25:43.952740090 +0000
    @@ -4,5 +4,5 @@
    gem 'awesome_print', :require => 'ap'

minitest - workaround until Rails 4.0 (#2650)

  • gem 'minitest', '~> 4.7'
    +# gem 'minitest', '~> 4.7'
    end
    ---------------------X8--------------------------
    I installed the appropriate rpm but still get an error so I commented it
    out. Hopefully I don't need it :wink: .

I also needed to install the following rpms as they were not dependent on
any other rpm:

  • foreman-assets
  • ruby193-rubygem-hirb-unicode
  • ruby193-rubygem-awesome_print
  • ruby193-rubygem-minitest

Besides the bundle.d/* files are not tracked by rpm. I hope this is as
expected.

Might be that I missed something, cause of the many rounds before being
there.

I hope this helps a bit to improve the rpms.

Next is add plugins.

Thanks Marc.

··· On Thursday, June 27, 2013 5:52:58 PM UTC+2, Lukas Zapletal wrote: > > On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote: > > `strict_error': Gem loading error: cannot load such file -- rack/openid > > Bundler_ext tries to require gemname, then if there is a dash in the > name it also tries with /. > > Try to use :require => in the Gemfile to specify correct require > statement. Bundler_ext respects that. > > LZ > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >
10

> Besides the bundle.d/* files are not tracked by rpm. I hope this is as
> expected.

What you mean by that? Which files? Can you provide an output of the
rpm verify command?

LZ

··· On Fri, Jun 28, 2013 at 01:45:35AM -0700, Marc Grimme wrote:

Might be that I missed something, cause of the many rounds before being
there.

I hope this helps a bit to improve the rpms.

Next is add plugins.

Thanks Marc.
On Thursday, June 27, 2013 5:52:58 PM UTC+2, Lukas Zapletal wrote:

On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote:

`strict_error’: Gem loading error: cannot load such file – rack/openid

Bundler_ext tries to require gemname, then if there is a dash in the
name it also tries with /.

Try to use :require => in the Gemfile to specify correct require
statement. Bundler_ext respects that.

LZ

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

–
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.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

11

I was wrong. There are no bundle.d files I described. I don't know where
they came from but certainly not from the rpm. Sorry about that.
Marc.

··· 2013/6/28 Lukas Zapletal

On Fri, Jun 28, 2013 at 01:45:35AM -0700, Marc Grimme wrote:

Besides the bundle.d/* files are not tracked by rpm. I hope this is as
expected.

What you mean by that? Which files? Can you provide an output of the
rpm verify command?

LZ

Might be that I missed something, cause of the many rounds before being
there.

I hope this helps a bit to improve the rpms.

Next is add plugins.

Thanks Marc.
On Thursday, June 27, 2013 5:52:58 PM UTC+2, Lukas Zapletal wrote:

On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote:

`strict_error’: Gem loading error: cannot load such file –
rack/openid

Bundler_ext tries to require gemname, then if there is a dash in the
name it also tries with /.

Try to use :require => in the Gemfile to specify correct require
statement. Bundler_ext respects that.

LZ

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

–
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.

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe.
To unsubscribe from this group and all its topics, 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.

12

They should be supplied, mostly by the subpackages, e.g. foreman-mysql
supplies ~foreman/bundler.d/mysql.rb.

I'm a bit confused as to what's gone wrong on your installation, I
haven't heard of this happening before. We've seen a number of
successful upgrades on the IRC channel.

··· -- Dominic Cleal Red Hat Engineering

On 28/06/13 12:39, Marc Grimme wrote:

I was wrong. There are no bundle.d files I described. I don’t know where
they came from but certainly not from the rpm. Sorry about that.
Marc.

2013/6/28 Lukas Zapletal <lzap@redhat.com mailto:lzap@redhat.com>

On Fri, Jun 28, 2013 at 01:45:35AM -0700, Marc Grimme wrote:
> Besides the bundle.d/* files are not tracked by rpm. I hope this is as
> expected.

What you mean by that? Which files? Can you provide an output of the
rpm verify command?

LZ

>
> Might be that I missed something, cause of the many rounds before
being
> there.
>
> I hope this helps a bit to improve the rpms.
>
> Next is add plugins.
>
> Thanks Marc.
> On Thursday, June 27, 2013 5:52:58 PM UTC+2, Lukas Zapletal wrote:
> >
> > On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote:
> > > `strict_error': Gem loading error: cannot load such file --
rack/openid
> >
> > Bundler_ext tries to require gemname, then if there is a dash in the
> > name it also tries with /.
> >
> > Try to use :require => in the Gemfile to specify correct require
> > statement. Bundler_ext respects that.
> >
> > LZ
> >
> > --
> > Later,
> >
> >  Lukas "lzap" Zapletal
> >  irc: lzap #theforeman
> >
>
> --
> 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
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
> To post to this group, send email to
foreman-users@googlegroups.com <mailto: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.
>
>

--
Later,

 Lukas "lzap" Zapletal
 irc: lzap #theforeman

--
You received this message because you are subscribed to a topic in
the Google Groups "Foreman users" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to foreman-users@googlegroups.com
<mailto: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.

–
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.

13

I think those problems were due to my errors. I validated the update on
another server and everything went ok, except the minitest gem.

Besides now I'm having problems to update mod_passenger with apache.

I've already removed the old rpms and installed ruby193-mod_passenger with
deps.

Mod_passenger seems to be installed just fine, but I think the
configuration with ruby193 needs to be rewritten.

How should I proceed?

Or did I do anything wrong?

Thanks Marc.

··· 2013/6/28 Dominic Cleal

They should be supplied, mostly by the subpackages, e.g. foreman-mysql
supplies ~foreman/bundler.d/mysql.rb.

I’m a bit confused as to what’s gone wrong on your installation, I
haven’t heard of this happening before. We’ve seen a number of
successful upgrades on the IRC channel.

–
Dominic Cleal
Red Hat Engineering

On 28/06/13 12:39, Marc Grimme wrote:

I was wrong. There are no bundle.d files I described. I don’t know where
they came from but certainly not from the rpm. Sorry about that.
Marc.

2013/6/28 Lukas Zapletal <lzap@redhat.com mailto:lzap@redhat.com>

On Fri, Jun 28, 2013 at 01:45:35AM -0700, Marc Grimme wrote:
> Besides the bundle.d/* files are not tracked by rpm. I hope this

is as

> expected.

What you mean by that? Which files? Can you provide an output of the
rpm verify command?

LZ

>
> Might be that I missed something, cause of the many rounds before
being
> there.
>
> I hope this helps a bit to improve the rpms.
>
> Next is add plugins.
>
> Thanks Marc.
> On Thursday, June 27, 2013 5:52:58 PM UTC+2, Lukas Zapletal wrote:
> >
> > On Thu, Jun 27, 2013 at 04:50:57AM -0700, Marc Grimme wrote:
> > > `strict_error': Gem loading error: cannot load such file --
rack/openid
> >
> > Bundler_ext tries to require gemname, then if there is a dash in

the

> > name it also tries with /.
> >
> > Try to use :require => in the Gemfile to specify correct require
> > statement. Bundler_ext respects that.
> >
> > LZ
> >
> > --
> > Later,
> >
> >  Lukas "lzap" Zapletal
> >  irc: lzap #theforeman
> >
>
> --
> 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
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
> To post to this group, send email to
foreman-users@googlegroups.com <mailto:

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.
>
>

--
Later,

 Lukas "lzap" Zapletal
 irc: lzap #theforeman

--
You received this message because you are subscribed to a topic in
the Google Groups "Foreman users" group.
To unsubscribe from this topic, visit

https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe.

To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com
<mailto:foreman-users%2Bunsubscribe@googlegroups.com>.
To post to this group, send email to foreman-users@googlegroups.com
<mailto: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.

–
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.

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe.
To unsubscribe from this group and all its topics, 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.

14

> I think those problems were due to my errors. I validated the update on
> another server and everything went ok, except the minitest gem.

Ah good. That's a known issue in foreman-console in RC3, see the change
here:

http://projects.theforeman.org/issues/2701

> Besides now I'm having problems to update mod_passenger with apache.
>
> I've already removed the old rpms and installed ruby193-mod_passenger
> with deps.
>
> Mod_passenger seems to be installed just fine, but I think the
> configuration with ruby193 needs to be rewritten.
>
> How should I proceed?
>
> Or did I do anything wrong?

Have you gone through the upgrade instructions in the manual?
http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages
(scroll down a bit)

What you should actually end up with is both ruby193-* and non-ruby193
passenger packages, so seven in total and all version 4.0.5 (from our
repo). There's a list of them in this section along with a few other
bits of config to check:
http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections

··· On 28/06/13 13:44, Marc Grimme wrote:

–
Dominic Cleal
Red Hat Engineering

15

Perfect. Everything fine now.

Thanks.
Even my plugins get installed.

··· 2013/6/28 Dominic Cleal

On 28/06/13 13:44, Marc Grimme wrote:

I think those problems were due to my errors. I validated the update on
another server and everything went ok, except the minitest gem.

Ah good. That’s a known issue in foreman-console in RC3, see the change
here:

Bug #2701: Error when foreman-console is installed: cannot load such file -- minitest - Foreman

Besides now I’m having problems to update mod_passenger with apache.

I’ve already removed the old rpms and installed ruby193-mod_passenger
with deps.

Mod_passenger seems to be installed just fine, but I think the
configuration with ruby193 needs to be rewritten.

How should I proceed?

Or did I do anything wrong?

Have you gone through the upgrade instructions in the manual?
Foreman :: Manual
(scroll down a bit)

What you should actually end up with is both ruby193-* and non-ruby193
passenger packages, so seven in total and all version 4.0.5 (from our
repo). There’s a list of them in this section along with a few other
bits of config to check:
Foreman :: Manual

–
Dominic Cleal
Red Hat Engineering

–
You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe.
To unsubscribe from this group and all its topics, 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.

16

Now it looks like some kind of problem with mod_passenger.

As I only need deface as additional gem for the plugins to be running I put
it in a local directory /usr/src/ruby/deface (Git clone). I checked out
Version 0.9.1 of deface.

The I created a bundle.d/deface.rb (just for testing, later on it will be
in the plugin Gemfile) as follows:

gem 'deface', :path => "/usr/src/ruby/deface"

When I start foreman as foreman user with
scl enable ruby193 './script/rails s --environment=production'

Everything works fine and I can access the foreman homepage.

When I use passenger with apache I get the following error:

Gem loading error: cannot load such file – deface (RuntimeError)
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in strict_error&#39; /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:inrescue in block in system_require'
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:in block in system_require&#39; /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:ineach'
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in system_require&#39; /usr/share/foreman/config/application.rb:11:in<top (required)>'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in require&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
/usr/share/foreman/config/environment.rb:2:in &lt;top (required)&gt;&#39; /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:inrequire'
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in require&#39; config.ru:3:inblock in <main>'
/opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in instance_eval&#39; /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:ininitialize'
config.ru:1:in new&#39; config.ru:1:in<main>'
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in eval&#39; /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:inpreload_app'
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:127:in &lt;module:App&gt;&#39; /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:6:in<module:PhusionPassenger>'
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:5:in `<main>'

My passenger configuration looks as follows:
cat /etc/httpd/conf.d/foreman.conf
#SetEnv GEM_PATH /usr/share/foreman/localgems
<VirtualHost *:80>
ServerName …

DocumentRoot /usr/share/foreman/public
PassengerAppRoot /usr/share/foreman
PassengerRuby /usr/bin/ruby193-ruby

#RailsAutoDetect On
AddDefaultCharset UTF-8

</VirtualHost>

No SSL right now.

Any ideas on how to proceed?

Thanks Marc.

··· On Friday, June 28, 2013 3:41:59 PM UTC+2, Marc Grimme wrote: > > Perfect. Everything fine now. > > Thanks. > Even my plugins get installed. > > > 2013/6/28 Dominic Cleal <dcl...@redhat.com > > >> On 28/06/13 13:44, Marc Grimme wrote: >> > I think those problems were due to my errors. I validated the update on >> > another server and everything went ok, except the minitest gem. >> >> Ah good. That's a known issue in foreman-console in RC3, see the change >> here: >> >> http://projects.theforeman.org/issues/2701 >> >> > Besides now I'm having problems to update mod_passenger with apache. >> > >> > I've already removed the old rpms and installed ruby193-mod_passenger >> > with deps. >> > >> > Mod_passenger seems to be installed just fine, but I think the >> > configuration with ruby193 needs to be rewritten. >> > >> > How should I proceed? >> > >> > Or did I do anything wrong? >> >> Have you gone through the upgrade instructions in the manual? >> http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages >> (scroll down a bit) >> >> What you should actually end up with is both ruby193-* and non-ruby193 >> passenger packages, so seven in total and all version 4.0.5 (from our >> repo). There's a list of them in this section along with a few other >> bits of config to check: >> http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections >> >> -- >> Dominic Cleal >> Red Hat Engineering >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Foreman users" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> foreman-user...@googlegroups.com . >> To post to this group, send email to forema...@googlegroups.com >> . >> Visit this group at http://groups.google.com/group/foreman-users. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >
17

Unfortunately, bundler_ext does not support :path.

LZ

··· On Mon, Jul 01, 2013 at 07:59:27AM -0700, Marc Grimme wrote: > Now it looks like some kind of problem with mod_passenger. > > As I only need deface as additional gem for the plugins to be running I put > it in a local directory /usr/src/ruby/deface (Git clone). I checked out > Version 0.9.1 of deface. > > The I created a bundle.d/deface.rb (just for testing, later on it will be > in the plugin Gemfile) as follows: > > gem 'deface', :path => "/usr/src/ruby/deface" > > When I start foreman as foreman user with > scl enable ruby193 './script/rails s --environment=production' > > Everything works fine and I can access the foreman homepage. > > When I use passenger with apache I get the following error: > > Gem loading error: cannot load such file -- deface (RuntimeError) > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in `strict_error' > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:in `rescue in block in system_require' > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:in `block in system_require' > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in `each' > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in `system_require' > /usr/share/foreman/config/application.rb:11:in `' > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' > /usr/share/foreman/config/environment.rb:2:in `' > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in `require' > config.ru:3:in `block in ' > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in `instance_eval' > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in `initialize' > config.ru:1:in `new' > config.ru:1:in `' > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in `eval' > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in `preload_app' > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:127:in `' > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:6:in `' > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:5:in `' > > > My passenger configuration looks as follows: > cat /etc/httpd/conf.d/foreman.conf > #SetEnv GEM_PATH /usr/share/foreman/localgems > > ServerName ... > > DocumentRoot /usr/share/foreman/public > PassengerAppRoot /usr/share/foreman > PassengerRuby /usr/bin/ruby193-ruby > > #RailsAutoDetect On > AddDefaultCharset UTF-8 > > > > No SSL right now. > > Any ideas on how to proceed? > > Thanks Marc. > > On Friday, June 28, 2013 3:41:59 PM UTC+2, Marc Grimme wrote: > > > > Perfect. Everything fine now. > > > > Thanks. > > Even my plugins get installed. > > > > > > 2013/6/28 Dominic Cleal <dcl...@redhat.com > > > > >> On 28/06/13 13:44, Marc Grimme wrote: > >> > I think those problems were due to my errors. I validated the update on > >> > another server and everything went ok, except the minitest gem. > >> > >> Ah good. That's a known issue in foreman-console in RC3, see the change > >> here: > >> > >> http://projects.theforeman.org/issues/2701 > >> > >> > Besides now I'm having problems to update mod_passenger with apache. > >> > > >> > I've already removed the old rpms and installed ruby193-mod_passenger > >> > with deps. > >> > > >> > Mod_passenger seems to be installed just fine, but I think the > >> > configuration with ruby193 needs to be rewritten. > >> > > >> > How should I proceed? > >> > > >> > Or did I do anything wrong? > >> > >> Have you gone through the upgrade instructions in the manual? > >> http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages > >> (scroll down a bit) > >> > >> What you should actually end up with is both ruby193-* and non-ruby193 > >> passenger packages, so seven in total and all version 4.0.5 (from our > >> repo). There's a list of them in this section along with a few other > >> bits of config to check: > >> http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections > >> > >> -- > >> Dominic Cleal > >> Red Hat Engineering > >> > >> -- > >> You received this message because you are subscribed to a topic in the > >> Google Groups "Foreman users" group. > >> To unsubscribe from this topic, visit > >> https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe. > >> To unsubscribe from this group and all its topics, send an email to > >> foreman-user...@googlegroups.com . > >> To post to this group, send email to forema...@googlegroups.com > >> . > >> Visit this group at http://groups.google.com/group/foreman-users. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > >> > > > > -- > 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. > >

–
Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

18

;-(

But how should I work around that problem?

Or put it otherway: How to install the deface gem on a RPM based
Installation with mod_passenger?

Shall I install the gems from a gem file with scl … gem install <gemfile>?

Thanks Marc.

··· On Monday, July 1, 2013 5:03:45 PM UTC+2, Lukas Zapletal wrote: > > Unfortunately, bundler_ext does not support :path. > > LZ > > On Mon, Jul 01, 2013 at 07:59:27AM -0700, Marc Grimme wrote: > > Now it looks like some kind of problem with mod_passenger. > > > > As I only need deface as additional gem for the plugins to be running I > put > > it in a local directory /usr/src/ruby/deface (Git clone). I checked out > > Version 0.9.1 of deface. > > > > The I created a bundle.d/deface.rb (just for testing, later on it will > be > > in the plugin Gemfile) as follows: > > > > gem 'deface', :path => "/usr/src/ruby/deface" > > > > When I start foreman as foreman user with > > scl enable ruby193 './script/rails s --environment=production' > > > > Everything works fine and I can access the foreman homepage. > > > > When I use passenger with apache I get the following error: > > > > Gem loading error: cannot load such file -- deface (RuntimeError) > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in > `strict_error' > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:in > `rescue in block in system_require' > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:in > `block in system_require' > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in > `each' > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in > `system_require' > > /usr/share/foreman/config/application.rb:11:in `' > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > `require' > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > `require' > > /usr/share/foreman/config/environment.rb:2:in `' > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > `require' > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > `require' > > config.ru:3:in `block in ' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in > `instance_eval' > > > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in > `initialize' > > config.ru:1:in `new' > > config.ru:1:in `' > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in > `eval' > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in > `preload_app' > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:127:in > `' > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:6:in > `' > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:5:in > `' > > > > > > My passenger configuration looks as follows: > > cat /etc/httpd/conf.d/foreman.conf > > #SetEnv GEM_PATH /usr/share/foreman/localgems > > > > ServerName ... > > > > DocumentRoot /usr/share/foreman/public > > PassengerAppRoot /usr/share/foreman > > PassengerRuby /usr/bin/ruby193-ruby > > > > #RailsAutoDetect On > > AddDefaultCharset UTF-8 > > > > > > > > No SSL right now. > > > > Any ideas on how to proceed? > > > > Thanks Marc. > > > > On Friday, June 28, 2013 3:41:59 PM UTC+2, Marc Grimme wrote: > > > > > > Perfect. Everything fine now. > > > > > > Thanks. > > > Even my plugins get installed. > > > > > > > > > 2013/6/28 Dominic Cleal <dcl...@redhat.com > > > > > > >> On 28/06/13 13:44, Marc Grimme wrote: > > >> > I think those problems were due to my errors. I validated the > update on > > >> > another server and everything went ok, except the minitest gem. > > >> > > >> Ah good. That's a known issue in foreman-console in RC3, see the > change > > >> here: > > >> > > >> http://projects.theforeman.org/issues/2701 > > >> > > >> > Besides now I'm having problems to update mod_passenger with > apache. > > >> > > > >> > I've already removed the old rpms and installed > ruby193-mod_passenger > > >> > with deps. > > >> > > > >> > Mod_passenger seems to be installed just fine, but I think the > > >> > configuration with ruby193 needs to be rewritten. > > >> > > > >> > How should I proceed? > > >> > > > >> > Or did I do anything wrong? > > >> > > >> Have you gone through the upgrade instructions in the manual? > > >> http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages > > >> (scroll down a bit) > > >> > > >> What you should actually end up with is both ruby193-* and > non-ruby193 > > >> passenger packages, so seven in total and all version 4.0.5 (from our > > >> repo). There's a list of them in this section along with a few other > > >> bits of config to check: > > >> http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections > > >> > > >> -- > > >> Dominic Cleal > > >> Red Hat Engineering > > >> > > >> -- > > >> You received this message because you are subscribed to a topic in > the > > >> Google Groups "Foreman users" group. > > >> To unsubscribe from this topic, visit > > >> > https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe. > > >> To unsubscribe from this group and all its topics, send an email to > > >> foreman-user...@googlegroups.com . > > >> To post to this group, send email to forema...@googlegroups.com > > > >> . > > >> Visit this group at http://groups.google.com/group/foreman-users. > > >> For more options, visit https://groups.google.com/groups/opt_out. > > >> > > >> > > >> > > > > > > > -- > > 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-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com. > > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > > -- > Later, > > Lukas "lzap" Zapletal > irc: lzap #theforeman >
19

Yes, that'll work, it just means you can't use a gem from a local path
or git install. (Actually, this was a change from bundler to
bundler_ext, just coincidental that we also changed to SCL.)

··· -- Dominic Cleal Red Hat Engineering

On 01/07/13 16:08, Marc Grimme wrote:

;-(

But how should I work around that problem?

Or put it otherway: How to install the deface gem on a RPM based
Installation with mod_passenger?

Shall I install the gems from a gem file with scl … gem install ?

Thanks Marc.

On Monday, July 1, 2013 5:03:45 PM UTC+2, Lukas Zapletal wrote:

Unfortunately, bundler_ext does not support :path.

LZ

On Mon, Jul 01, 2013 at 07:59:27AM -0700, Marc Grimme wrote:
> Now it looks like some kind of problem with mod_passenger.
>
> As I only need deface as additional gem for the plugins to be
running I put
> it in a local directory /usr/src/ruby/deface (Git clone). I
checked out
> Version 0.9.1 of deface.
>
> The I created a bundle.d/deface.rb (just for testing, later on it
will be
> in the plugin Gemfile) as follows:
>
> gem 'deface', :path => "/usr/src/ruby/deface"
>
> When I start foreman as foreman user with
> scl enable ruby193 './script/rails s --environment=production'
>
> Everything works fine and I can access the foreman homepage.
>
> When I use passenger with apache I get the following error:
>
> Gem loading error: cannot load such file -- deface (RuntimeError)
>  
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in
`strict_error'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:in
`rescue in block in system_require'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:in
`block in system_require'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
`each'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in
`system_require'
>   /usr/share/foreman/config/application.rb:11:in `<top (required)>'
>  
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
`require'
>  
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
`require'
>   /usr/share/foreman/config/environment.rb:2:in `<top (required)>'
>  
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
`require'
>  
/opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in
`require'
>   config.ru:3:in `block in <main>'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in
`instance_eval'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in
`initialize'
>   config.ru:1:in `new'
>   config.ru:1:in `<main>'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in
`eval'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in
`preload_app'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:127:in
`<module:App>'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:6:in
`<module:PhusionPassenger>'
>  
/opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:5:in
`<main>'
>
>  
> My passenger configuration looks as follows:
> cat /etc/httpd/conf.d/foreman.conf
> #SetEnv GEM_PATH /usr/share/foreman/localgems
> <VirtualHost *:80>
>   ServerName ...
>
>   DocumentRoot /usr/share/foreman/public
>   PassengerAppRoot /usr/share/foreman
>   PassengerRuby /usr/bin/ruby193-ruby
>
>   #RailsAutoDetect On
>   AddDefaultCharset UTF-8
>
> </VirtualHost>
>
> No SSL right now.
>
> Any ideas on how to proceed?
>
> Thanks Marc.
>
> On Friday, June 28, 2013 3:41:59 PM UTC+2, Marc Grimme wrote:
> >
> > Perfect. Everything fine now.
> >
> > Thanks.
> > Even my plugins get installed.
> >
> >
> > 2013/6/28 Dominic Cleal <dcl...@redhat.com <javascript:>>
> >
> >> On 28/06/13 13:44, Marc Grimme wrote:
> >> > I think those problems were due to my errors. I validated the
update on
> >> > another server and everything went ok, except the minitest gem.
> >>
> >> Ah good.  That's a known issue in foreman-console in RC3, see
the change
> >> here:
> >>
> >> http://projects.theforeman.org/issues/2701
<http://projects.theforeman.org/issues/2701>
> >>
> >> > Besides now I'm having problems to update mod_passenger with
apache.
> >> >
> >> > I've already removed the old rpms and installed
ruby193-mod_passenger
> >> > with deps.
> >> >
> >> > Mod_passenger seems to be installed just fine, but I think the
> >> > configuration with ruby193 needs to be rewritten.
> >> >
> >> > How should I proceed?
> >> >
> >> > Or did I do anything wrong?
> >>
> >> Have you gone through the upgrade instructions in the manual?
> >> http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages
<http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages>
> >> (scroll down a bit)
> >>
> >> What you should actually end up with is both ruby193-* and
non-ruby193
> >> passenger packages, so seven in total and all version 4.0.5
(from our
> >> repo).  There's a list of them in this section along with a few
other
> >> bits of config to check:
> >>
http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections <http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections>

> >>
> >> --
> >> Dominic Cleal
> >> Red Hat Engineering
> >>
> >> --
> >> You received this message because you are subscribed to a topic
in the
> >> Google Groups "Foreman users" group.
> >> To unsubscribe from this topic, visit
> >>
https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe
<https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe>.

> >> To unsubscribe from this group and all its topics, send an
email to
> >> foreman-user...@googlegroups.com <javascript:>.
> >> To post to this group, send email to
forema...@googlegroups.com<javascript:>
> >> .
> >> Visit this group at
http://groups.google.com/group/foreman-users
<http://groups.google.com/group/foreman-users>.
> >> For more options, visit
https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
> >>
> >>
> >>
> >
>
> --
> 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-user...@googlegroups.com <javascript:>.
> To post to this group, send email to forema...@googlegroups.com
<javascript:>.
> Visit this group at http://groups.google.com/group/foreman-users
<http://groups.google.com/group/foreman-users>.
> For more options, visit https://groups.google.com/groups/opt_out
<https://groups.google.com/groups/opt_out>.
>
>

-- 
Later,

 Lukas "lzap" Zapletal
 irc: lzap #theforeman

–
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.

20

That did it. Great.
I installed the gems with --ignore-dependencies and now everything looks
like its working.
Thanks very much.

Regards Marc.

··· On Monday, July 1, 2013 5:11:48 PM UTC+2, Dominic Cleal wrote: > > Yes, that'll work, it just means you can't use a gem from a local path > or git install. (Actually, this was a change from bundler to > bundler_ext, just coincidental that we also changed to SCL.) > > -- > Dominic Cleal > Red Hat Engineering > > On 01/07/13 16:08, Marc Grimme wrote: > > ;-( > > > > But how should I work around that problem? > > > > Or put it otherway: How to install the deface gem on a RPM based > > Installation with mod_passenger? > > > > Shall I install the gems from a gem file with scl .. gem install > ? > > > > Thanks Marc. > > > > On Monday, July 1, 2013 5:03:45 PM UTC+2, Lukas Zapletal wrote: > > > > Unfortunately, bundler_ext does not support :path. > > > > LZ > > > > On Mon, Jul 01, 2013 at 07:59:27AM -0700, Marc Grimme wrote: > > > Now it looks like some kind of problem with mod_passenger. > > > > > > As I only need deface as additional gem for the plugins to be > > running I put > > > it in a local directory /usr/src/ruby/deface (Git clone). I > > checked out > > > Version 0.9.1 of deface. > > > > > > The I created a bundle.d/deface.rb (just for testing, later on it > > will be > > > in the plugin Gemfile) as follows: > > > > > > gem 'deface', :path => "/usr/src/ruby/deface" > > > > > > When I start foreman as foreman user with > > > scl enable ruby193 './script/rails s --environment=production' > > > > > > Everything works fine and I can access the foreman homepage. > > > > > > When I use passenger with apache I get the following error: > > > > > > Gem loading error: cannot load such file -- deface (RuntimeError) > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:30:in > > > `strict_error' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:56:in > > > `rescue in block in system_require' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:37:in > > > `block in system_require' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in > > > `each' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/bundler_ext-0.3.0/lib/bundler_ext/bundler_ext.rb:35:in > > > `system_require' > > > /usr/share/foreman/config/application.rb:11:in ` (required)>' > > > > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > > `require' > > > > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > > `require' > > > /usr/share/foreman/config/environment.rb:2:in `' > > > > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > > `require' > > > > > > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:36:in > > `require' > > > config.ru:3:in `block in ' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in > > > `instance_eval' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in > > > `initialize' > > > config.ru:1:in `new' > > > config.ru:1:in `' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in > > > `eval' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:82:in > > > `preload_app' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:127:in > > > `' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:6:in > > > `' > > > > > > /opt/rh/ruby193/root/usr/share/gems/gems/passenger-4.0.5/helper-scripts/rack-preloader.rb:5:in > > > `' > > > > > > > > > My passenger configuration looks as follows: > > > cat /etc/httpd/conf.d/foreman.conf > > > #SetEnv GEM_PATH /usr/share/foreman/localgems > > > > > > ServerName ... > > > > > > DocumentRoot /usr/share/foreman/public > > > PassengerAppRoot /usr/share/foreman > > > PassengerRuby /usr/bin/ruby193-ruby > > > > > > #RailsAutoDetect On > > > AddDefaultCharset UTF-8 > > > > > > > > > > > > No SSL right now. > > > > > > Any ideas on how to proceed? > > > > > > Thanks Marc. > > > > > > On Friday, June 28, 2013 3:41:59 PM UTC+2, Marc Grimme wrote: > > > > > > > > Perfect. Everything fine now. > > > > > > > > Thanks. > > > > Even my plugins get installed. > > > > > > > > > > > > 2013/6/28 Dominic Cleal <dcl...@redhat.com > > > > > > > > >> On 28/06/13 13:44, Marc Grimme wrote: > > > >> > I think those problems were due to my errors. I validated the > > update on > > > >> > another server and everything went ok, except the minitest > gem. > > > >> > > > >> Ah good. That's a known issue in foreman-console in RC3, see > > the change > > > >> here: > > > >> > > > >> http://projects.theforeman.org/issues/2701 > > > > > >> > > > >> > Besides now I'm having problems to update mod_passenger with > > apache. > > > >> > > > > >> > I've already removed the old rpms and installed > > ruby193-mod_passenger > > > >> > with deps. > > > >> > > > > >> > Mod_passenger seems to be installed just fine, but I think > the > > > >> > configuration with ruby193 needs to be rewritten. > > > >> > > > > >> > How should I proceed? > > > >> > > > > >> > Or did I do anything wrong? > > > >> > > > >> Have you gone through the upgrade instructions in the manual? > > > >> http://theforeman.org/manuals/1.2/index.html#3.3.1RPMPackages > > > > > >> (scroll down a bit) > > > >> > > > >> What you should actually end up with is both ruby193-* and > > non-ruby193 > > > >> passenger packages, so seven in total and all version 4.0.5 > > (from our > > > >> repo). There's a list of them in this section along with a few > > other > > > >> bits of config to check: > > > >> > > > http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections < > http://theforeman.org/manuals/1.2/index.html#3.3.2SoftwareCollections> > > > > > >> > > > >> -- > > > >> Dominic Cleal > > > >> Red Hat Engineering > > > >> > > > >> -- > > > >> You received this message because you are subscribed to a topic > > in the > > > >> Google Groups "Foreman users" group. > > > >> To unsubscribe from this topic, visit > > > >> > > > https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe > > < > https://groups.google.com/d/topic/foreman-users/FLd41k7qWg4/unsubscribe>. > > > > > >> To unsubscribe from this group and all its topics, send an > > email to > > > >> foreman-user...@googlegroups.com . > > > >> To post to this group, send email to > > forema...@googlegroups.com > > > >> . > > > >> Visit this group at > > http://groups.google.com/group/foreman-users > > . > > > >> For more options, visit > > https://groups.google.com/groups/opt_out > > . > > > >> > > > >> > > > >> > > > > > > > > > > -- > > > 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-user...@googlegroups.com . > > > To post to this group, send email to forema...@googlegroups.com > > . > > > Visit this group at http://groups.google.com/group/foreman-users > > . > > > For more options, visit https://groups.google.com/groups/opt_out > > . > > > > > > > > > > -- > > Later, > > > > Lukas "lzap" Zapletal > > irc: lzap #theforeman > > > > -- > > 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-user...@googlegroups.com . > > To post to this group, send email to forema...@googlegroups.com. > > > Visit this group at http://groups.google.com/group/foreman-users. > > For more options, visit https://groups.google.com/groups/opt_out. > > > > > >