Foreman 1.2 installation issues (via RPM packages)

I've opted to install Foreman 1.2 on a fully updated CentOS 6.4.
The instructions (@
Foreman :: Manual) were
not very clear.

  1. Is Postgresql required? It's not an RPM dependency (makes sense, I
    guess), but I presume I need 'foreman-postgresql' , as 'foreman' itself is
    not sufficient?

  2. There are no instructions for basic configuration of Postgresql. At
    least a pointer to what is needed would be helpful for first-timers.

  3. The instructions for setup should lead to how to configure. "Configure
    by editing /etc/foreman/settings.yaml and /etc/foreman/database.yml" is not
    enough - a pointer to what needs to be configured (which seems to be
    written further down) would be helpful.

  4. And thus, running 'service foreman start' without a clue what needs to
    be configured ends up with:
    [root@foreman foreman]# service foreman start
    Starting foreman:
    /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in
    to_specs': Please install the sqlite3 adapter:gem install
    activerecord-sqlite3-adapter(Could not find sqlite3 (~> 1.3.5) amongst [actionmailer-3.2.8, actionpack-3.2.8, activemodel-3.2.8, activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8, ancestry-1.3.0, apipie-rails-0.0.18, arel-3.0.2, audited-3.0.0, audited-activerecord-3.0.0, bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, bundler_ext-0.3.0, coffee-rails-3.2.2, coffee-script-2.2.0, coffee-script-source-1.3.3, daemons-1.1.4, diff-lcs-1.1.3, erubis-2.7.0, eventmachine-0.12.10, excon-0.20.1, execjs-1.4.0, fast_gettext-0.5.10, fog-1.11.1, foremancli-1.0, formatador-0.2.1, gettext_i18n_rails-0.9.4, gettext_i18n_rails_js-0.0.8, hike-1.2.1, i18n-0.6.0, i18n_data-0.2.7, io-console-0.3, journey-1.0.4, jquery-rails-2.0.2, jquery-ui-rails-4.0.2, json-1.5.4, mail-2.4.4, mime-types-1.19, multi_json-1.3.6, net-http-persistent-2.7, net-ldap-0.2.2, net-scp-1.1.0, net-ssh-2.6.7, nokogiri-1.5.6, oauth-0.4.7, pg-0.12.2, po_to_json-0.0.7, polyglot-0.3.3, rabl-0.7.6, rack-1.4.1, rack-cache-1.2, rack-ssl-1.3.2, rack-test-0.6.1, rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbvmomi-1.6.0, rdoc-3.12, ref-1.0.0, rest-client-1.6.1, ruby-hmac-0.4.0, ruby2ruby-2.0.1, ruby_parser-3.1.1, safemode-1.2.0, sass-3.1.20, sass-rails-3.2.5, scoped_search-2.5.1, sexp_processor-4.1.3, sprockets-2.4.5, therubyracer-0.11.0beta5, thin-1.3.1, thor-0.15.4, tilt-1.3.3, treetop-1.4.10, trollop-2.0, twitter-bootstrap-rails-2.2.6, tzinfo-0.3.33, uglifier-1.2.6, uuidtools-2.1.3, will_paginate-3.0.2]) (LoadError) from /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:into_spec'
    from /opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:in
    gem&#39; from /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3: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'

  5. It's not clear if puppet is needed or not (I understood it's needed for
    the installer, not sure about the packages and it's not a dependency).

I'd expect the installation of 'foreman-postgresql' to change the settings
to postgresql by default.

Should I file a bug on the documentation?

I'll try to make things work and document more first-timer's issues I
stumble upon. Or I'll try the installer.

Thanks,
Y.

Hi Yaniv,

Generally we'd recommend using the Foreman Installer for your first install

  • it does use the packages underneath, but also does all the setup for you.
    See Foreman :: Manual for how to get started.
    I'll still address your points inline though:

> 1. Is Postgresql required? It's not an RPM dependency (makes sense, I
> guess), but I presume I need 'foreman-postgresql' , as 'foreman' itself is
> not sufficient?
>
A DB of some sort is required (psql, mysql, or sqlite3) - the Installer
defaults to postgres, and will install and configure a postgres server for
you by default. This behaviour of the installer can be customised.

> 2. There are no instructions for basic configuration of Postgresql. At
> least a pointer to what is needed would be helpful for first-timers.
>
Again, we'd recommend new Foreman users to use the Installer.

> 3. The instructions for setup should lead to how to configure. "Configure
> by editing /etc/foreman/settings.yaml and /etc/foreman/database.yml" is not
> enough - a pointer to what needs to be configured (which seems to be
> written further down) would be helpful.
>
Also covered by the installer.

In general, I'd recommend a basic install via the quickstart on a vm - even
if you don't like the exact setup, you'll have a working machine to compare
to if you still want to do the setup by hand.

However, the documentation can always be improved, so thanks for taking the
time to feedback! Patches are always welcome, if you want to submit a PR
for where we can do better.

Cheers,
Greg

··· On 10 July 2013 19:42, Yaniv Kaul wrote:

(How do you post inline in Google groups?!)

I've moved to using the installer, and it was quite swift and easy.
Now I'm missing the chapter 'Now that you've installed Foreman, here's how
to add your first host' .
There's no 'Getting started using Foreman' that I could find.

Y.

··· On Wednesday, July 10, 2013 8:42:08 PM UTC+3, Yaniv Kaul wrote: > > I've opted to install Foreman 1.2 on a fully updated CentOS 6.4. > The instructions (@ > http://theforeman.org/manuals/1.2/index.html#3.3InstallFromPackages) were > not very clear. > 1. Is Postgresql required? It's not an RPM dependency (makes sense, I > guess), but I presume I need 'foreman-postgresql' , as 'foreman' itself is > not sufficient? > 2. There are no instructions for basic configuration of Postgresql. At > least a pointer to what is needed would be helpful for first-timers. > 3. The instructions for setup should lead to how to configure. "Configure > by editing /etc/foreman/settings.yaml and /etc/foreman/database.yml" is not > enough - a pointer to what needs to be configured (which seems to be > written further down) would be helpful. > 4. And thus, running 'service foreman start' without a clue what needs to > be configured ends up with: > [root@foreman foreman]# service foreman start > Starting foreman: > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in > `to_specs': Please install the sqlite3 adapter: `gem install > activerecord-sqlite3-adapter` (Could not find sqlite3 (~> 1.3.5) amongst > [actionmailer-3.2.8, actionpack-3.2.8, activemodel-3.2.8, > activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8, > ancestry-1.3.0, apipie-rails-0.0.18, arel-3.0.2, audited-3.0.0, > audited-activerecord-3.0.0, bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, > bundler_ext-0.3.0, coffee-rails-3.2.2, coffee-script-2.2.0, > coffee-script-source-1.3.3, daemons-1.1.4, diff-lcs-1.1.3, erubis-2.7.0, > eventmachine-0.12.10, excon-0.20.1, execjs-1.4.0, fast_gettext-0.5.10, > fog-1.11.1, foremancli-1.0, formatador-0.2.1, gettext_i18n_rails-0.9.4, > gettext_i18n_rails_js-0.0.8, hike-1.2.1, i18n-0.6.0, i18n_data-0.2.7, > io-console-0.3, journey-1.0.4, jquery-rails-2.0.2, jquery-ui-rails-4.0.2, > json-1.5.4, mail-2.4.4, mime-types-1.19, multi_json-1.3.6, > net-http-persistent-2.7, net-ldap-0.2.2, net-scp-1.1.0, net-ssh-2.6.7, > nokogiri-1.5.6, oauth-0.4.7, pg-0.12.2, po_to_json-0.0.7, polyglot-0.3.3, > rabl-0.7.6, rack-1.4.1, rack-cache-1.2, rack-ssl-1.3.2, rack-test-0.6.1, > rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbvmomi-1.6.0, rdoc-3.12, > ref-1.0.0, rest-client-1.6.1, ruby-hmac-0.4.0, ruby2ruby-2.0.1, > ruby_parser-3.1.1, safemode-1.2.0, sass-3.1.20, sass-rails-3.2.5, > scoped_search-2.5.1, sexp_processor-4.1.3, sprockets-2.4.5, > therubyracer-0.11.0beta5, thin-1.3.1, thor-0.15.4, tilt-1.3.3, > treetop-1.4.10, trollop-2.0, twitter-bootstrap-rails-2.2.6, tzinfo-0.3.33, > uglifier-1.2.6, uuidtools-2.1.3, will_paginate-3.0.2]) (LoadError) > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:in > `to_spec' > from /opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:in > `gem' > from > /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3:in > `' > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in > `require' > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in > `rescue in require' > > > 5. It's not clear if puppet is needed or not (I understood it's needed for > the installer, not sure about the packages and it's not a dependency). > > I'd expect the installation of 'foreman-postgresql' to change the settings > to postgresql by default. > > Should I file a bug on the documentation? > > I'll try to make things work and document more first-timer's issues I > stumble upon. Or I'll try the installer. > > Thanks, > Y. >

I just did an install of Foreman 1.2 on a fresh CENT 6.4 and have no issues.
just followed the manual replacing the Repo instead of 1.1 to 1.2.

··· On Wednesday, July 10, 2013 1:42:08 PM UTC-4, Yaniv Kaul wrote: > > I've opted to install Foreman 1.2 on a fully updated CentOS 6.4. > The instructions (@ > http://theforeman.org/manuals/1.2/index.html#3.3InstallFromPackages) were > not very clear. > 1. Is Postgresql required? It's not an RPM dependency (makes sense, I > guess), but I presume I need 'foreman-postgresql' , as 'foreman' itself is > not sufficient? > 2. There are no instructions for basic configuration of Postgresql. At > least a pointer to what is needed would be helpful for first-timers. > 3. The instructions for setup should lead to how to configure. "Configure > by editing /etc/foreman/settings.yaml and /etc/foreman/database.yml" is not > enough - a pointer to what needs to be configured (which seems to be > written further down) would be helpful. > 4. And thus, running 'service foreman start' without a clue what needs to > be configured ends up with: > [root@foreman foreman]# service foreman start > Starting foreman: > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:247:in > `to_specs': Please install the sqlite3 adapter: `gem install > activerecord-sqlite3-adapter` (Could not find sqlite3 (~> 1.3.5) amongst > [actionmailer-3.2.8, actionpack-3.2.8, activemodel-3.2.8, > activerecord-3.2.8, activeresource-3.2.8, activesupport-3.2.8, > ancestry-1.3.0, apipie-rails-0.0.18, arel-3.0.2, audited-3.0.0, > audited-activerecord-3.0.0, bigdecimal-1.1.0, builder-3.0.0, bundler-1.1.4, > bundler_ext-0.3.0, coffee-rails-3.2.2, coffee-script-2.2.0, > coffee-script-source-1.3.3, daemons-1.1.4, diff-lcs-1.1.3, erubis-2.7.0, > eventmachine-0.12.10, excon-0.20.1, execjs-1.4.0, fast_gettext-0.5.10, > fog-1.11.1, foremancli-1.0, formatador-0.2.1, gettext_i18n_rails-0.9.4, > gettext_i18n_rails_js-0.0.8, hike-1.2.1, i18n-0.6.0, i18n_data-0.2.7, > io-console-0.3, journey-1.0.4, jquery-rails-2.0.2, jquery-ui-rails-4.0.2, > json-1.5.4, mail-2.4.4, mime-types-1.19, multi_json-1.3.6, > net-http-persistent-2.7, net-ldap-0.2.2, net-scp-1.1.0, net-ssh-2.6.7, > nokogiri-1.5.6, oauth-0.4.7, pg-0.12.2, po_to_json-0.0.7, polyglot-0.3.3, > rabl-0.7.6, rack-1.4.1, rack-cache-1.2, rack-ssl-1.3.2, rack-test-0.6.1, > rails-3.2.8, railties-3.2.8, rake-0.9.2.2, rbvmomi-1.6.0, rdoc-3.12, > ref-1.0.0, rest-client-1.6.1, ruby-hmac-0.4.0, ruby2ruby-2.0.1, > ruby_parser-3.1.1, safemode-1.2.0, sass-3.1.20, sass-rails-3.2.5, > scoped_search-2.5.1, sexp_processor-4.1.3, sprockets-2.4.5, > therubyracer-0.11.0beta5, thin-1.3.1, thor-0.15.4, tilt-1.3.3, > treetop-1.4.10, trollop-2.0, twitter-bootstrap-rails-2.2.6, tzinfo-0.3.33, > uglifier-1.2.6, uuidtools-2.1.3, will_paginate-3.0.2]) (LoadError) > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/dependency.rb:256:in > `to_spec' > from /opt/rh/ruby193/root/usr/share/rubygems/rubygems.rb:1231:in > `gem' > from > /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/sqlite3_adapter.rb:3:in > `' > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in > `require' > from > /opt/rh/ruby193/root/usr/share/rubygems/rubygems/custom_require.rb:60:in > `rescue in require' > > > 5. It's not clear if puppet is needed or not (I understood it's needed for > the installer, not sure about the packages and it's not a dependency). > > I'd expect the installation of 'foreman-postgresql' to change the settings > to postgresql by default. > > Should I file a bug on the documentation? > > I'll try to make things work and document more first-timer's issues I > stumble upon. Or I'll try the installer. > > Thanks, > Y. >

> Hi Yaniv,
>
> Generally we'd recommend using the Foreman Installer for your first
> install - it does use the packages underneath, but also does all the setup
> for you. See Foreman :: Manual for how to
> get started. I'll still address your points inline though:
>
>
>> 1. Is Postgresql required? It's not an RPM dependency (makes sense, I
>> guess), but I presume I need 'foreman-postgresql' , as 'foreman' itself is
>> not sufficient?
>>
> A DB of some sort is required (psql, mysql, or sqlite3) - the Installer
> defaults to postgres, and will install and configure a postgres server for
> you by default. This behaviour of the installer can be customised.
>
>
>> 2. There are no instructions for basic configuration of Postgresql. At
>> least a pointer to what is needed would be helpful for first-timers.
>>
> Again, we'd recommend new Foreman users to use the Installer.
>

If you're just generally interested in how the DB is configured, check out
this excellent guide -
https://github.com/ekohl/foreman-howto/blob/master/README.rst. The
installer is still the recommended way to setup a completely fresh instance.

··· On Wed, Jul 10, 2013 at 10:31 PM, Greg Sutcliffe wrote: > On 10 July 2013 19:42, Yaniv Kaul wrote:
  1. The instructions for setup should lead to how to configure. “Configure
    by editing /etc/foreman/settings.yaml and /etc/foreman/database.yml” is not
    enough - a pointer to what needs to be configured (which seems to be
    written further down) would be helpful.

Also covered by the installer.

In general, I’d recommend a basic install via the quickstart on a vm -
even if you don’t like the exact setup, you’ll have a working machine to
compare to if you still want to do the setup by hand.

However, the documentation can always be improved, so thanks for taking
the time to feedback! Patches are always welcome, if you want to submit a
PR for where we can do better.

Cheers,
Greg


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.

> (How do you post inline in Google groups?!)

I'm using Gmail since I'm subscribed to the list :slight_smile:

> I've moved to using the installer, and it was quite swift and easy.
> Now I'm missing the chapter 'Now that you've installed Foreman, here's how
> to add your first host' .
> There's no 'Getting started using Foreman' that I could find.
>

Rather than a long explanation, you probably want to watch this video:
http://www.youtube.com/watch?v=2dwyzPpFJYQ&feature=player_embedded in which
Dominic goes through the setup and first puppet run of a new Foreman host.

Greg

··· On 11 July 2013 09:13, Yaniv Kaul wrote:

>
>> (How do you post inline in Google groups?!)
>
>
> I'm using Gmail since I'm subscribed to the list :slight_smile:
>

OK, got it.

>
>
>> I've moved to using the installer, and it was quite swift and easy.
>> Now I'm missing the chapter 'Now that you've installed Foreman, here's
>> how to add your first host' .
>> There's no 'Getting started using Foreman' that I could find.
>>
>
> Rather than a long explanation, you probably want to watch this video:
> http://www.youtube.com/watch?v=2dwyzPpFJYQ&feature=player_embedded in
> which Dominic goes through the setup and first puppet run of a new Foreman
> host.
>
> Greg
>

Excellent. The Youtube was just what I was looking for. Managed to get my
environment up and running (and broke it 10 minutes later, still debugging).
Y.

··· On Thursday, July 11, 2013 10:22:06 AM UTC+3, Greg Sutcliffe wrote: > On 11 July 2013 09:13, Yaniv Kaul <myk...@gmail.com > wrote: