Red Hat Bugzilla – Bug 809824
katello-configure with no deployment option returns unfriendly error.
Last modified: 2014-11-09 17:55:55 EST
Description of problem:
When running katello-configure there is no obvious default deployment type; however, rather than explaining that deployment type should be passed a err is returned that is no user friendly.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum install -y katello-headpin-all
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20120404-091126/main.log]
err: /Stage[main]/Mongodb::Service/Service[mongod]/ensure: change from stopped to running failed: Could not start Service[mongod]: Execution of '/sbin/service mongod start' returned 1: at /usr/share/katello/install/puppet/modules/mongodb/manifests/service.pp:5
err: /Stage[main]/Certs::Config/Exec[strip-qpid-client-certificate]/returns: change from notrun to 0 failed: cp /root/ssl-build/mgmt9.rhq.lab.eng.bos.redhat.com/qpid-client.key /etc/pki/pulp/qpid_client_striped.crt; openssl x509 -in /root/ssl-build/mgmt9.rhq.lab.eng.bos.redhat.com/qpid-client.crt >> /etc/pki/pulp/qpid_client_striped.crt returned 1 instead of one of  at /usr/share/katello/install/puppet/modules/certs/manifests/config.pp:311
err: /File[/var/lib/pulp/packages]/ensure: change from absent to directory failed: Cannot create /var/lib/pulp/packages; parent directory /var/lib/pulp does not exist
Error explaining that a deployment type must be specified.
Duplicate of 809823; "katello" is the default deployment which is why you get these errors
*** This bug has been marked as a duplicate of bug 809823 ***