ERROR 2019-04-16T11:59:13 main] Execution of ‘/usr/sbin/foreman-rake – config -k ‘puppetdb_dashboard_address’ -v ‘http://localhost:8080/pdb/dashboard’’ returned 1: /usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP
(Many ERRORs follow …)
[root@foreman10125 ~]# foreman-rake SmartProxy.pulp_master
/usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP
/usr/share/foreman/lib/foreman.rb:8: warning: previous definition of UUID_REGEXP was here
rake aborted!
Don’t know how to build task ‘SmartProxy.pulp_master’ (see --tasks)
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.0/exe/rake:27:in `<top (required)>’
(See full trace by running task with --trace)
rake aborted!
NoMethodError: undefined method settings_type' for nil:NilClass /usr/share/foreman/lib/tasks/config.rake:105:inblock in run_key_values’
/usr/share/foreman/lib/tasks/config.rake:100:in each' /usr/share/foreman/lib/tasks/config.rake:100:inrun_key_values’
/usr/share/foreman/lib/tasks/config.rake:77:in run' /usr/share/foreman/lib/tasks/config.rake:167:inblock in <top (required)>’
/opt/rh/rh-ruby25/root/usr/share/gems/gems/rake-12.3.0/exe/rake:27:in `<top (required)>’
Tasks: TOP => config
(See full trace by running task with --trace)
One more question:
What command do I run with the --trace option?
It’s not part of foreman-installer, nor foreman-rake.
This command failed and you want to run it manually in order to see what error it gives. but I think you mispasted it I do not see matching quotes correctly and I am not sure if it is complete. Maybe @ekohl knows more details for this puppet step.
[ERROR 2019-04-16T11:59:13 main] /Stage[main]/Foreman::Plugin::Puppetdb/Foreman_config_entry[puppetdb_dashboard_address]/value: change from ‘’ to ‘http://localhost:8080/pdb/dashboard’ failed: Execution of ‘/usr/sbin/foreman-rake – config -k ‘puppetdb_dashboard_address’ -v ‘http://localhost:8080/pdb/dashboard’’ returned 1: /usr/share/foreman/lib/foreman.rb:8: warning: already initialized constant Foreman::UUID_REGEXP
But I am wondering if I even need puppetdb?
In a previous installation, I set puppetdb_enabled = No in the Foreman Settings to get around an issue when trying to delete a host.
Changing the answers file should never be needed. If you do, you found a bug. You can run foreman-installer --no-enable-foreman-plugin-puppetdb but that unmanages it. It doesn’t actually clean up. I think yum remove foreman-plugin-puppetdb might break because it could leave some database changes behind. Someone with more knowledge of the core can probably answer that.
My fear is that using --no-enable-foreman-plugin-puppetdb will still try to install it (build, make, whatever), then not enable it. I might be forced to start over from a fresh VM and clean installation without puppetdb.
Important: Not only remove the affected line, but also a block which the line starts
Also very important: In the puppet manifests the documentation part with dashboard must also be removed, because the installer checks it!
Wit the changed manifests the cache is outdated, so the installer needs to check the modules again, but fails to do so, if puppet-strings is not installed, so install it with puppet’s gem: