Plugins » Katello

This error appears to have come about this week, as test installs last week didn't do this.

Main Config Menu
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_remote_execution
11. [â] Configure foreman_plugin_setup
12. [â] Configure foreman_plugin_tasks
13. [â] Configure foreman_plugin_templates
14. [â] Configure katello
15. [â] Configure katello_plugin_gutterball
16. Display current config
17. Save and run
18. Cancel run without Saving
Choose an option from the menu... 17
echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for :5432/postgres]/returns: change from notrun to 0 failed: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for :5432/postgres]: Failed to call refresh: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Postgresql::Server::Service/Postgresql::Validate_db_connection[validate_service_is_running]/Exec[validate postgres connection for @:5432/postgres]: echo 'Unable to connect to defined database using: /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres ' && false returned 1 instead of one of [0]
/Stage[main]/Gutterball::Database/Exec[migrate database]: Failed to call refresh: Could not find command 'gutterball-db'
/Stage[main]/Gutterball::Database/Exec[migrate database]: Could not find command 'gutterball-db'
/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]/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:index]/Exec[foreman-rake-apipie:cache:index]: Failed to call refresh: /usr/sbin/foreman-rake apipie:cache:index returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache:index]/Exec[foreman-rake-apipie:cache:index]: /usr/sbin/foreman-rake apipie:cache:index returned 1 instead of one of [0]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pxaa2katello01m0.z2.linux.argosretailgroup.com]: Failed to call refresh: Proxy pxaa2katello01m0.z2.linux.argosretailgroup.com cannot be registered (Could not load data from https://pxaa2katello01m0.z2.linux.argosretailgroup.com
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[pxaa2katello01m0.z2.linux.argosretailgroup.com]: Proxy pxaa2katello01m0.z2.linux.argosretailgroup.com cannot be registered (Could not load data from https://pxaa2katello01m0.z2.linux.argosretailgroup.com
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

Full log attached.

Have tried including PostgreSQL as a service port to the firewalld with no effect, have also tested the connection afterwards via the postgres account, which seems fine.

su - postgres
Last login: Wed May 25 14:01:46 BST 2016 on pts/0
-bash-4.2$ /usr/bin/psql --tuples-only --quiet -p 5432 --dbname postgres
postgres=# \du;
gutterball | | {}
postgres | Superuser, Create role, Create DB, Replication | {}

postgres=#