Hide Forgot
Created attachment 555428 [details] sam deployment shell script. Description of problem: SAM deployment failed when run 'katello-configure --deployment=headpin'. Version-Release number of selected component (if applicable): katello-common-0.1.165-2.el6.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-cli-headpin-0.1.13-2.el6.noarch katello-certs-tools-1.0.1-2.el6.noarch katello-headpin-0.1.124-2.el6.noarch katello-trusted-ssl-cert-1.0-1.noarch katello-cli-common-0.1.32-2.el6.noarch katello-configure-0.1.49-2.el6.noarch katello-headpin-all-0.1.124-2.el6.noarch katello-httpd-ssl-key-pair-1.0-1.noarch katello-glue-candlepin-0.1.165-2.el6.noarch candlepin-0.5.8-1.el6.noarch candlepin-tomcat6-0.5.8-1.el6.noarch thumbslug-0.0.21-1.el6.noarch How reproducible: always Steps to Reproduce: 1. Install a vm with below url: http://download.englab.nay.redhat.com/pub/rhel/rel-eng/RHEL6.2-20111117.0/6.2/Server/x86_64/os/ 2. Log in the vm as root user. 3. Run the shell script 'samdeploy.sh', which has been enclosed into this bug as an attachment, to deploy SAM automatically. Actual results: When the shell script performs the command 'katello-configure --deployment=headpin', below error happens which effects the sam deployment failure: err: /Stage[main]/Katello::Config/Exec[katello_seed_db]/returns: change from notrun to 0 failed: /usr/bin/env rake db:seed --trace --verbose > /var/log/katello/katello-configure/db_seed.log 2>&1 && touch /var/lib/katello/db_seed_done returned 1 instead of one of [0] at /usr/share/katello/install/puppet/modules/katello/manifests/config.pp:186 Expected results: The sam deployment should be successful and no error occurs. Additional info: The log files have been enclosed as the attachment 'katello-configure-20120116-202553.zip'.
Created attachment 555429 [details] log file for the deployment failure.
Jordan: Can you let me know when the new build is in brew. If that installs, we can move this to modified.
Developers believe this is a duplicate of 783193. Be sure your SAM install is on a full Virt guest. this appears to be performance related and is easily reproduced on guests running in QEMU. closing as a duplicate of 783193. *** This bug has been marked as a duplicate of bug 783193 ***