SOLVED. There was a warning in the install log. [root@katello ~]# grep WARN /var/log/katello-installer/katello-installer.[12].log | grep Def /var/log/katello-installer/katello-installer.1.log:[ WARN 2016-06-28 13:52:13 main] /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]/returns: Couldn't find Organization with name = Default Organization
Looks like you shouldn't remove the 'Default Organization'. Foreman shouldn't let you remove it if it needs it for other commands. But I'd rather be able to remove the Default Organization and not have commands rely on it though. My $0.02. On Tuesday, June 28, 2016 at 3:08:41 PM UTC-4, Edson Manners wrote: > > I'm adding a custom wildcard cert to my existing production Katello 2.4 > install on CentOS 7.2 using these instructions: > https://github.com/Katello/katello-installer#certificates > I've followed this other thread but he had an issue in his certs but mine > (GoDaddy) pass the test clean. > > The katello-certs-check succeeded, but when I run the resulting > katello-installer command for a currently running Katello installation I > get this error: > Marking certificate /root/ssl-build/katello-server-ca for update > > /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] > > > even though if I run foreman-rake db:seed independently it runs correctly: > [root@katello ~]# foreman-rake db:seed --trace > ** Invoke db:seed (first_time) > ** Execute db:seed > ** Invoke db:abort_if_pending_migrations (first_time) > ** Invoke environment (first_time) > ** Execute environment > ** Invoke db:load_config (first_time) > ** Execute db:load_config > ** Execute db:abort_if_pending_migrations > Seeding /usr/share/foreman/db/seeds.d/03-auth_sources.rb > Seeding /usr/share/foreman/db/seeds.d/03-permissions.rb > Seeding /usr/share/foreman/db/seeds.d/03-roles.rb > Seeding /usr/share/foreman/db/seeds.d/04-admin.rb > Seeding /usr/share/foreman/db/seeds.d/05-taxonomies.rb > Seeding /usr/share/foreman/db/seeds.d/06-architectures.rb > Seeding /usr/share/foreman/db/seeds.d/07-provisioning_templates.rb > Seeding /usr/share/foreman/db/seeds.d/08-partition_tables.rb > Seeding /usr/share/foreman/db/seeds.d/10-installation_media.rb > Seeding /usr/share/foreman/db/seeds.d/11-smart_proxy_features.rb > Seeding /usr/share/foreman/db/seeds.d/13-compute_profiles.rb > Seeding /usr/share/foreman/db/seeds.d/15-bookmarks.rb > Seeding /usr/share/foreman/db/seeds.d/16-mail_notifications.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.11/db/seeds.d/20-foreman_tasks_permissions.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_bootdisk-6.1.0/db/seeds.d/50-bootdisk_templates.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.2/db/seeds.d/50_discovery_templates.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.11/db/seeds.d/60-dynflow_proxy_feature.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman_discovery-4.1.2/db/seeds.d/60_discovery_proxy_feature.rb > Seeding > /opt/theforeman/tfm/root/usr/share/gems/gems/foreman-tasks-0.7.11/db/seeds.d/61-foreman_tasks_bookmarks.rb > All seed files executed > > The WebGUI certs seem to install correctly though as the web browser > recognizes it however the local capsule that runs puppet, puppetca, tftp > and bmc on the server no longer connects. > [root@katello katello-installer]# katello-installer --certs-server-cert > "/etc/pki/katello/certs/rcc.fsu.edu.cer"\ > > --certs-server-cert-req > "/etc/pki/katello/csr/rcc.fsu.edu.csr"\ > > --certs-server-key > "/etc/pki/katello/private/rcc.fsu.edu.key"\ > > --certs-server-ca-cert > "/etc/pki/katello/certs/ca.pem"\ > > --certs-update-server --certs-update-server-ca > Marking certificate /root/ssl-build/ > katello.rcc.fsu.edu/katello.rcc.fsu.edu-apache for update > Marking certificate /root/ssl-build/ > katello.rcc.fsu.edu/katello.rcc.fsu.edu-foreman-proxy for update > Marking certificate /root/ssl-build/katello-server-ca for update > > /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_proxy::Register/Foreman_smartproxy[ > katello.rcc.fsu.edu]: Could not evaluate: Proxy katello.rcc.fsu.edu > cannot be registered (503 Service Unavailable): N/A > 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 > > > ------------------------------------------------------------------------------------ > > Here is the tails of the installer.lo > > [ INFO 2016-06-28 14:01:40 main] All hooks in group post finished > [DEBUG 2016-06-28 14:01:40 main] Exit with status code: 6 (signal was 6) > [ERROR 2016-06-28 14:01:40 main] Repeating errors encountered during run: > [ERROR 2016-06-28 14:01:40 main] > > /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] > [ERROR 2016-06-28 14:01:40 main] > > /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] > [ERROR 2016-06-28 14:01:40 main] > /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[ > katello.rcc.fsu.edu]: Could not evaluate: Proxy katello.rcc.fsu.edu > cannot be registered (503 Service Unavailable): N/A > [DEBUG 2016-06-28 14:01:40 main] Cleaning > /etc/katello-installer/d20160628-15904-mwu582 > [DEBUG 2016-06-28 14:01:40 main] Cleaning /tmp/default_values.yaml > > And the local proxy is in fact running: > [root@katello katello-installer]# systemctl status foreman-proxy > ● foreman-proxy.service - Foreman Proxy > Loaded: loaded (/usr/lib/systemd/system/foreman-proxy.service; enabled; > vendor preset: disabled) > Active: active (running) since Tue 2016-06-28 10:59:09 EDT; 4h 6min ago > Process: 717 ExecStart=/usr/share/foreman-proxy/bin/smart-proxy > (code=exited, status=0/SUCCESS) > Main PID: 725 (ruby) > CGroup: /system.slice/foreman-proxy.service > └─725 ruby /usr/share/foreman-proxy/bin/smart-proxy > > Jun 28 10:59:07 katello.rcc.fsu.edu systemd[1]: Stopping Foreman Proxy... > Jun 28 10:59:07 katello.rcc.fsu.edu systemd[1]: Starting Foreman Proxy... > Jun 28 10:59:09 katello.rcc.fsu.edu systemd[1]: PID file > /run/foreman-proxy/foreman-proxy.pid not readable (yet?) after start. > Jun 28 10:59:09 katello.rcc.fsu.edu systemd[1]: Started Foreman Proxy. > > Any ideas. It's a production machine and I tried to go back by > regenerating the self-signed certs but that gave the same error so I'm > stuck trying to make the custom certs work. > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
