Bug #12910
closedInstallation issues
Description
During the installation on CentOS 7 i am getting several Problems:
After following the instructions on:
http://www.katello.org/docs/2.4/installation/index.html
i have installed katello with warnings:
---
warning: group tomcat does not exist - using root
warning: user tomcat does not exist - using root
---
Installation of katello was successful.
In the next step i run katello-installer -i with followed options:
1. [✓] Configure capsule
2. [✓] Configure certs
3. [✓] Configure foreman
4. [✗] Configure foreman_plugin_bootdisk
5. [✗] Configure foreman_plugin_chef
6. [✓] Configure foreman_plugin_default_hostgroup
7. [✓] Configure foreman_plugin_discovery
8. [✓] Configure foreman_plugin_hooks
9. [✓] Configure foreman_plugin_puppetdb
10. [✗] Configure foreman_plugin_setup
11. [✓] Configure foreman_plugin_tasks
12. [✗] Configure foreman_plugin_templates
13. [✓] Configure katello
14. [✗] Configure katello_plugin_gutterball
15. Display current config
During the Installation am getting more errors:
Could not start Service[mongodb]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait start mongod' returned 1: Redirecting to /bin/systemctl start mongod.service
/Stage[main]/Mongodb::Server::Service/Service[mongodb]/ensure: change from stopped to running failed: Could not start Service[mongodb]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait start mongod' returned 1: Redirecting to /bin/systemctl start mongod.service
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: Failed to call refresh: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[db:migrate]/Exec[foreman-rake-db:migrate]: /usr/sbin/foreman-rake db:migrate returned 1 instead of one of [0]
/Stage[main]/Pulp::Database/Exec[migrate_pulp_db]: Failed to call refresh: Command exceeded timeout
/Stage[main]/Pulp::Database/Exec[migrate_pulp_db]: Command exceeded timeout
/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[lcm.nodes.rto.de]: Failed to call refresh: Proxy lcm.nodes.rto.de cannot be registered (Could not load data from https://lsecret.hostname.com
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[lcm.nodes.rto.de]: Proxy lcm.nodes.rto.de cannot be registered (Could not load data from https://lsecret.hostname.com
See installer log!
I understand that the project is very complex to build, but please provide a seemless installation on CentOS 7 cause im trying to install katello since version 2.3 and im still getting errors!
Files
Updated by Denis Müller over 9 years ago
Im trying to debug the Problem:
service mongod was able to start manually, but i took some long time to do it. I thing during the installation there is a timeout so it skips this step.
Im still can't start apache, caouse of missing /var/lib/puppet/ssl/ca/ca_crt.pem.
Updated by Denis Müller over 9 years ago
[root@lcm ~]# /usr/sbin/foreman-rake db:migrate
Performance on MRI may be improved with the concurrent-ruby-ext gem. Please see http://concurrent-ruby.com
AddForeignKeysEngine: migrating =========================================
-- add_foreign_key("katello_activation_keys", "katello_content_views", {:column=>"content_view_id", :name=>"activation_keys_content_view_id_fk"})
rake aborted!
An error has occurred, all later migrations canceled:
Mysql2::Error: Can't create table 'foreman.#sql-1c45_85' (errno: 121): ALTER TABLE `katello_activation_keys` ADD CONSTRAINT `activation_keys_content_view_id_fk` FOREIGN KEY (`content_view_id`) REFERENCES `katello_content_views`(id)
Tasks: TOP => db:migrate
(See full trace by running task with --trace)
Updated by Justin Sherrill over 9 years ago
- Translation missing: en.field_release changed from 70 to 113
Updated by David Davis about 9 years ago
- Status changed from New to Need more information
One of the big things I notice is that you're trying to use mysql and we don't support that. Could you maybe retry with postgresql?
I'm not totally sure about the mongo errors. How much memory does your box have?
Updated by Justin Sherrill about 9 years ago
- Status changed from Need more information to Rejected
- Translation missing: en.field_release deleted (
113)
Closing this as it seems related to mysql. Feel free to reopen if you disagree.
Updated by Justin Sherrill almost 9 years ago
- Translation missing: en.field_release set to 166