Horribly Newbie Questions -- Katello/Foreman

Support
1

Hi gang!

Sorry in advance, but I've been desperately trying to find walk-throughs
and tutorials on how to do this …

Here's the low-down first. I am trying to organize / manage 4 new (bare
metal) machines I have in a rack in a development test lab. I, obviously,
want to manage them in a cool modern way. :slight_smile: These machines will be used
to try out new technologies, development systems, etc. using either VM's
(one sort or another) and/or Docker to try out containers, etc.

I would love to be able to manage the whole life-cycle of these 4 machines
– and after kicking some tires (Spacewalk notably) decided to give
Katello/Foreman a go. After some false (many) starts – I decided to start
clean again.

So basically, I'd like to set up one server as the "head" node that would
contain boot images (as needed), be the Katello/Foreman "master", NTP
master, etc. etc. for the "cluster" as well as to be a member of the
compute set. The other 3 machines would be just "compute" nodes (I think).

I would like to install Katello … and set it up so that I can PXE boot for
discovery the other 3 machines into Foreman and have it load the OS (All
Centos 6.6) and basic configuration, etc.

Is this reasonable and do-able? Is there a nice set of Katello tutorials?
Heck, I'm not even positive the difference or what Katello adds to Foreman
… Doh. :slight_smile:

Any pointers to beginning doc for newbie dev ops trying to do this would be
awesome.

TIA!

/Steve

2

BTW – I just installed Katello via the git deploy script – and during the
actual "katello-installer" command, at about 99% done … I am getting these
error messages:

/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead
of one of [0]

/Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]:
/usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]

/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
Failed to call refresh: /usr/sbin/foreman-rake apipie:cache returned 1
instead of one of [0]

/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]:
/usr/sbin/foreman-rake apipie:cache returned 1 instead of one of [0]

Are these important? The installer continued on after pausing about 15
seconds …

Then after a few more minutes I get this error:

/usr/share/foreman/script/foreman-config -k ssl_ca_file -v
'/etc/foreman/proxy_ca.pem' -k ssl_certificate -v
'/etc/foreman/client_cert.pem' -k ssl_priv_key -v
'/etc/foreman/client_key.pem' returned 1 instead of one of [0]

/Stage[main]/Certs::Foreman/Exec[foreman_certs_config]/returns: change
from notrun to 0 failed: /usr/share/foreman/script/foreman-config -k
ssl_ca_file -v '/etc/foreman/proxy_ca.pem' -k ssl_certificate -v
'/etc/foreman/client_cert.pem' -k ssl_priv_key -v
'/etc/foreman/client_key.pem' returned 1 instead of one of [0]

/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ws-head.galaxysemi.com]:
Could not evaluate: Could not load data from https://ws-head.galaxysemi.com

/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ws-head.galaxysemi.com]:
Failed to call refresh: Could not load data from
https://ws-head.galaxysemi.com

/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ws-head.galaxysemi.com]:
Could not load data from https://ws-head.galaxysemi.com

Finally it completed with :

Installing Done
[100%] […]

Something went wrong! Check the log for ERROR-level output

The full log is at /var/log/katello-installer/katello-installer.log

This makes me a bit nervous that the install didn't actually work?

Well, it apparently didn't work since when I try to access the web site I
am getting:
Web application could not be started

some permissions were not found (ArgumentError)
/usr/share/foreman/app/models/role.rb:126:in add_permissions' /usr/share/foreman/app/models/role.rb:141:inadd_permissions!'
/usr/share/foreman/app/services/foreman/plugin.rb:187:in block in role' /opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:192:intransaction'
/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/transactions.rb:208:in transaction' /usr/share/foreman/app/services/foreman/plugin.rb:185:inrole'
/opt/rh/ruby193/root/usr/share/gems/gems/foreman_bootdisk-3.2.1/lib/foreman_bootdisk/engine.rb:39:in block (2 levels) in <class:Engine>' /usr/share/foreman/app/services/foreman/plugin.rb:61:ininstance_eval'
/usr/share/foreman/app/services/foreman/plugin.rb:61:in register&#39; /opt/rh/ruby193/root/usr/share/gems/gems/foreman_bootdisk-3.2.1/lib/foreman_bootdisk/engine.rb:31:inblock in <class:Engine>'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in instance_exec&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:inrun'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:55:in block in run_initializers&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:ineach'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in run_initializers&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:136:ininitialize!'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:in method_missing&#39; /usr/share/foreman/config/environment.rb:5: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'
config.ru:3:in block in &lt;main&gt;&#39; /opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:ininstance_eval'
/opt/rh/ruby193/root/usr/share/gems/gems/rack-1.4.1/lib/rack/builder.rb:51:in initialize&#39; config.ru:1:innew'
config.ru:1:in &lt;main&gt;&#39; /usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/helper-scripts/rack-preloader.rb:105:ineval'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/helper-scripts/rack-preloader.rb:105:in preload_app&#39; /usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/helper-scripts/rack-preloader.rb:150:in<module:App>'
/usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/helper-scripts/rack-preloader.rb:29:in &lt;module:PhusionPassenger&gt;&#39; /usr/lib/ruby/gems/1.8/gems/passenger-4.0.18/helper-scripts/rack-preloader.rb:28:in<main>'

Application root/usr/share/foremanEnvironment (value of RAILS_ENV,
RACK_ENV, WSGI_ENV and PASSENGER_ENV)productionRuby interpreter command

/usr/bin/ruby193-ruby

User and groups

uid=498(foreman) gid=498(foreman) groups=498(foreman),52(puppet)

Ugh – and in the katello installer logs … I see this message (besides the above) :

··· ---

[ INFO 2014-11-25 15:09:19 main] RESOURCE Foreman_smartproxy[ws-head.galaxysemi.com]

[ INFO 2014-11-25 15:10:05 main] E, [2014-11-25T15:10:05.307871 #4253] ERROR – : 500 Internal Server Error

More errors (from before) :

[ERROR 2014-11-25 15:08:34 main] /Stage[main]/Certs::Foreman/Exec[foreman_certs_config]/returns: change from notrun to

0 failed: /usr/share/foreman/script/foreman-config -k ssl_ca_file -v ‘/etc/foreman/proxy_ca.pem’ -k ssl_certif

icate -v ‘/etc/foreman/client_cert.pem’ -k ssl_priv_key -v ‘/etc/foreman/client_key.pem’ returned 1 instead of one

of [0]

[ INFO 2014-11-25 15:08:34 main] RESOURCE Exec[foreman_certs_config]

[DEBUG 2014-11-25 15:08:34 main] Class[Certs::Foreman]: The container Stage[main] will propagate my refresh event

[ INFO 2014-11-25 15:09:19 main] E, [2014-11-25T15:09:19.834949 #4253] ERROR – : 500 Internal Server Error

[ INFO 2014-11-25 15:09:19 main] #<String:0x7fc574ba76b0

And yet another suspicious message that parallels the Web error:

[DEBUG 2014-11-25 15:07:49 main] Execforeman_certs_config: Executing '/usr/share/foreman/script/forem

an-config -k ssl_ca_file -v ‘/etc/foreman/proxy_ca.pem’ -k ssl_certificate -v ‘/etc/foreman/client_cert.pem’

-k ssl_priv_key -v '/etc/foreman/client_key.pem''

[DEBUG 2014-11-25 15:07:49 main] Executing '/usr/share/foreman/script/foreman-config -k ssl_ca_file -v '/etc/forem

an/proxy_ca.pem’ -k ssl_certificate -v ‘/etc/foreman/client_cert.pem’ -k ssl_priv_key -v '/etc/foreman/client_

key.pem’’

[ WARN 2014-11-25 15:08:34 main] /Stage[main]/Certs::Foreman/Exec[foreman_certs_config]/returns: /usr/share/foreman/app

/models/role.rb:126:in `add_permissions’: some permissions were not found (ArgumentError)

[ WARN 2014-11-25 15:08:34 main] /Stage[main]/Certs::Foreman/Exec[foreman_certs_config]/returns: from /usr/share/

foreman/app/models/role.rb:141:in `add_permissions!’

OK – I didn’t see any other errors scrolling backwards toward the start …

Sooo – Guess I need some extra help!

Thanks!

/Steve

3

I was able to re-create the initial error (and subsequent errors) by just
running foreman-rake db:seed by it's own with --trace. Hopefully this
helps someone. :slight_smile:

··· --

[root@ws-head ~]# foreman-rake --trace db:seed

** Invoke db:seed (first_time)

** Execute db:seed

** Invoke db:abort_if_pending_migrations (first_time)

** Invoke environment (first_time)

** Execute environment

rake aborted!

some permissions were not found

/usr/share/foreman/app/models/role.rb:126:in `add_permissions’

/usr/share/foreman/app/models/role.rb:141:in `add_permissions!’

/usr/share/foreman/app/services/foreman/plugin.rb:187:in `block in role’

/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in
`transaction’

/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/transactions.rb:208:in
`transaction’

/usr/share/foreman/app/services/foreman/plugin.rb:185:in `role’

/opt/rh/ruby193/root/usr/share/gems/gems/foreman_bootdisk-3.2.1/lib/foreman_bootdisk/engine.rb:39:in
`block (2 levels) in class:Engine’

/usr/share/foreman/app/services/foreman/plugin.rb:61:in `instance_eval’

/usr/share/foreman/app/services/foreman/plugin.rb:61:in `register’

/opt/rh/ruby193/root/usr/share/gems/gems/foreman_bootdisk-3.2.1/lib/foreman_bootdisk/engine.rb:31:in
`block in class:Engine’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in
`instance_exec’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in
`run’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:55:in
`block in run_initializers’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in
`each’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in
`run_initializers’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:136:in
`initialize!’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:in
`method_missing’

/usr/share/foreman/config/environment.rb:5: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’

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
`block in require’

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in
`load_dependency’

/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:in
`require’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:103:in
`require_environment!’

/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:295:in
`block (2 levels) in initialize_tasks’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `call’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `block in execute’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `each’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `execute’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in `block in
invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
`invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:in `block in
invoke_prerequisites’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in `each’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in
`invoke_prerequisites’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:in `block in
invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
`invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in `invoke’

/opt/rh/ruby193/root/usr/share/gems/gems/activerecord-3.2.8/lib/active_record/railties/databases.rake:308:in
`block (2 levels) in <top (required)>’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `call’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in `block in execute’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `each’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in `execute’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in `block in
invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:in `mon_synchronize’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
`invoke_with_call_chain’

/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:in `invoke’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in `invoke_task’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block (2
levels) in top_level’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `each’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in `block in
top_level’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
`standard_exception_handling’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:in `top_level’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in `block in run’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
`standard_exception_handling’

/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in `run’

/opt/rh/ruby193/root/usr/bin/rake:32:in `’

Tasks: TOP => db:abort_if_pending_migrations => environment

4

Is this not the right group for this question/problem? Should I ask in the
dev group? (I can't imagine that would be correct but…)

This seems to be a "simple" fundamental install issue … but what do I know
since I really don't know what I'm doing. LOL :slight_smile:

Anyway, any help would be appreciated!

Cheers and Happy T Day for those who celebrate that sort of thing! (Well,
it's tomorrow, but still…)

/Steve

5

SOLVED!!

Thanks to help from Dominic on the IRC I was able to resolve the basic
problem. Seems that during install (a known bug) there is a chance that
duplicate permissions are added to the DB.

To resolve:

Move the foreman_bootdisk.rb to someplace safe:

cd /usr/share/foreman/bundler.d

mv foreman_bootdisk.rb foreman_bootdisk.rb.ori

Start up the foreman console and verify the duplicate entry and then delete
the extra one …

foreman-rake console

> Permission.where(:name => 'download_bootdisk')

You will (hopefully) see a result set of TWO entries … (mine was IDs # 206
and 205 ) … Looking like:

=> [#<Permission id: 206, name: "download_bootdisk", resource_type: nil,
created_at: "2014-11-25 20:00:29", updated_at: "2014-11-25 20:00:29">,
#<Permission id: 205, name: "download_bootdisk", resource_type: nil,
created_at: "2014-11-25 20:00:29", updated_at: "2014-11-25 20:00:29">]

So now let's delete one!

> Permission.destroy(206)

That sound remove the extra …

Quit console … > quit

Then we'll almost done … we need to "ping" foreman that we need to do the
install again, "safely" … This is a bit of magic …

echo >> /etc/foreman/database.yml

And don't forget to move back the .rb file!

mv *ori foreman_bootdisk.rb

Finally run the katello-installer again with whatever options you had when
you did it the first time…

Hopefully all should work!

··· >
6

I am having the same problem but have only uncovered another one with the
sass gem.

I installed the sass gem but suspect I need to update a config file
somewhere to point to it.

[root@sj19-hh28-admin ~]# foreman-rake console --trace
Sass is in the process of being separated from Haml,
and will no longer be bundled at all in Haml 3.2.0.
Please install the 'sass' gem if you want to use Sass.

** Invoke console (first_time)
** Invoke environment (first_time)
** Execute environment
Apipie cache enabled but not present yet. Run apipie:cache rake task to
speed up API calls.
Workaround for RbVmomi may not work as ComputeResource is already loaded:
ComputeResource
rake aborted!
undefined method sass&#39; for #&lt;Rails::Application::Configuration:0x000000049a18f8&gt; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configuration.rb:85:inmethod_missing'
/opt/rh/ruby193/root/usr/share/gems/gems/katello-2.1.0/lib/katello/engine.rb:59:in
block in &lt;class:Engine&gt;&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:ininstance_exec'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:30:in
run&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:55:inblock in run_initializers'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:in
each&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/initializable.rb:54:inrun_initializers'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:136:in
initialize!&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/railtie/configurable.rb:30:inmethod_missing'
/usr/share/foreman/config/environment.rb:5: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; /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inblock in require '
/opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:236:in
load_dependency&#39; /opt/rh/ruby193/root/usr/share/gems/gems/activesupport-3.2.8/lib/active_support/dependencies.rb:251:inrequire'
/opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:103:in
require_environment!&#39; /opt/rh/ruby193/root/usr/share/gems/gems/railties-3.2.8/lib/rails/application.rb:295:inblock (2 levels) in initialize_ tasks'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:in call&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:205:inblock in execute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:in each&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:200:inexecute'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:158:in block in invoke_with_call_chain&#39; /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:176:inblock in
invoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:in each&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:174:ininvoke_prerequisites'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:157:in block in invoke_with_call_chain&#39; /opt/rh/ruby193/root/usr/share/ruby/monitor.rb:211:inmon_synchronize'
/opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:151:in
invoke_with_call_chain&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/task.rb:144:ininvoke'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:116:in invoke_task&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock (2
levels) in top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:in each&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:94:inblock in
top_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:in
standard_exception_handling&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:88:intop_level'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:66:in block in run&#39; /opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:133:instandard_exception_handling'
/opt/rh/ruby193/root/usr/share/ruby/rake/application.rb:63:in run&#39; /opt/rh/ruby193/root/usr/bin/rake:32:in<main>'
Tasks: TOP => console => environment

··· On Wednesday, November 26, 2014 8:11:58 AM UTC-8, Steven McDowall wrote: > > SOLVED!! > > Thanks to help from Dominic on the IRC I was able to resolve the basic > problem. Seems that during install (a known bug) there is a chance that > duplicate permissions are added to the DB. > > To resolve: > > Move the foreman_bootdisk.rb to someplace safe: > > cd /usr/share/foreman/bundler.d > > mv foreman_bootdisk.rb foreman_bootdisk.rb.ori > > > Start up the foreman console and verify the duplicate entry and then > delete the extra one .. > > > foreman-rake console > > > Permission.where(:name => 'download_bootdisk') > > > You will (hopefully) see a result set of TWO entries .. (mine was IDs # > 206 and 205 ) ... Looking like: > > => [# created_at: "2014-11-25 20:00:29", updated_at: "2014-11-25 20:00:29">, > # created_at: "2014-11-25 20:00:29", updated_at: "2014-11-25 20:00:29">] > > > So now let's delete one! > > > Permission.destroy(206) > > That sound remove the extra .. > > Quit console ... > quit > > Then we'll almost done .. we need to "ping" foreman that we need to do the > install again, "safely" ... This is a bit of magic .. > > # echo >> /etc/foreman/database.yml > > And don't forget to move back the .rb file! > > # mv *ori foreman_bootdisk.rb > > > Finally run the katello-installer again with whatever options you had when > you did it the first time.. > > > Hopefully all should work! > > > >>
7

> Is this not the right group for this question/problem? Should I ask in
> the dev group? (I can't imagine that would be correct but…)
>

This is indeed the right group to ask user questions :slight_smile: bug reports are
usually reported against our bugtracker, at [1] you can find a full list of
ways that you can get support at.

>
>

> This seems to be a "simple" fundamental install issue … but what do I
> know since I really don't know what I'm doing. LOL :slight_smile:
>
> Anyway, any help would be appreciated!
>
I'm sure that once someone who knows the answer read it, she / he would
answer… :slight_smile:

Ohad

[1] Foreman :: Support

··· On Wed, Nov 26, 2014 at 4:39 PM, Steven McDowall wrote:

Cheers and Happy T Day for those who celebrate that sort of thing! (Well,
it’s tomorrow, but still…)

/Steve

–
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/d/optout.