Bug 1013329 - Error: /usr/bin/rake db:migrate --trace --verbose
Summary: Error: /usr/bin/rake db:migrate --trace --verbose
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Installer
Version: Nightly
Hardware: Unspecified
OS: Unspecified
unspecified
high vote
Target Milestone: Unspecified
Assignee: David Davis
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-09-29 10:23 UTC by Magnus Glantz
Modified: 2019-09-26 13:42 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-05-05 17:23:55 UTC
Target Upstream Version:


Attachments (Terms of Use)
rpm -qa from my F18 server (21.97 KB, text/plain)
2013-09-29 10:23 UTC, Magnus Glantz
no flags Details
main.log from install (162.11 KB, text/plain)
2013-09-29 10:24 UTC, Magnus Glantz
no flags Details
katello-debug (110.99 KB, application/x-gzip)
2013-09-29 10:26 UTC, Magnus Glantz
no flags Details
katello-debug from rhel64 (78.24 KB, application/x-gzip)
2013-09-29 11:16 UTC, Magnus Glantz
no flags Details
main.log from install - rhel64 (161.79 KB, text/plain)
2013-09-29 11:17 UTC, Magnus Glantz
no flags Details
rpm -qa from my RHEL64 server (29.61 KB, text/plain)
2013-09-29 11:17 UTC, Magnus Glantz
no flags Details
My debug package from fedora 18 (118.92 KB, application/x-gzip)
2013-10-14 13:33 UTC, Håkan Hagenrud
no flags Details

Description Magnus Glantz 2013-09-29 10:23:37 UTC
Created attachment 804663 [details]
rpm -qa from my F18 server

Description of problem:
Katello install broken on Fedora 18, both in latest stable and yesterdays nightly.

Version-Release number of selected component (if applicable):
katello-1.4.8-1.git.4.c940d43.fc18.noarch
katello-all-1.4.8-1.git.4.c940d43.fc18.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-certs-tools-1.4.4-1.fc18.noarch
katello-cli-1.4.3-1.git.65.3b0dfd5.fc18.noarch
katello-cli-common-1.4.3-1.git.65.3b0dfd5.fc18.noarch
katello-common-1.4.8-1.git.4.c940d43.fc18.noarch
katello-configure-1.4.7-1.fc18.noarch
katello-glue-candlepin-1.4.8-1.git.4.c940d43.fc18.noarch
katello-glue-elasticsearch-1.4.8-1.git.4.c940d43.fc18.noarch
katello-glue-pulp-1.4.8-1.git.4.c940d43.fc18.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-repos-1.4.2-1.fc18.noarch
katello-selinux-1.4.4-1.git.2.863ea81.fc18.noarch
pulp-katello-plugins-0.2-1.fc18.noarch
signo-katello-0.0.21-1.fc18.noarch
rubygem-rake-0.9.2.2-2.fc18.1.noarch or rubygem-rake-0.9.6-1.fc18.noarch

See attached 'rpm -qa' for details.

How reproducible:
Reproducible all the time.

Steps to Reproduce:
1. Install Fedora 18 (minimal install) and update to latest stable
2. Turn off IPv6, turn off SELinux, set a proper FQDN.
3. Follow instructions on https://fedorahosted.org/katello/wiki/Install but with nightly katello repos.

Actual results:
After installation, katello and katello-jobs does not work.

Expected results:
A working installation.

Additional info:
The only problems I can see from the installation log is

130929-01:41:20 Error: /usr/bin/rake db:migrate --trace --verbose > /var/log/katello/katello-configure/db_migrate.log 2>&1 && touch /var/lib/katello/db_migrate_done returned 1 instead of one of [0]
130929-01:41:20 Error: /Stage[main]/Katello::Config/Exec[katello_migrate_db]/returns: change from notrun to 0 failed: /usr/bin/rake db:migrate --trace --verbose > /var/log/katello/katello-configure/db_migrate.log 2>&1 && touch /var/lib/katello/db_migrate_done returned 1 instead of one of [0]

My stab in the dark is that this is a path issue.

Comment 1 Magnus Glantz 2013-09-29 10:24:46 UTC
Created attachment 804664 [details]
main.log from install

Comment 2 Magnus Glantz 2013-09-29 10:26:00 UTC
Created attachment 804665 [details]
katello-debug

Comment 3 Magnus Glantz 2013-09-29 10:35:24 UTC
A more proper description of the end product is that after installation, katello and katello-jobs does not start up. No details in /var/log/messages on why.

Comment 4 Magnus Glantz 2013-09-29 11:12:51 UTC
I tried to replicate this on RHEL6.4 GA, but it works fine there.
Attaching debug/logs from the RHEL-server.

Comment 5 Magnus Glantz 2013-09-29 11:16:46 UTC
Created attachment 804667 [details]
katello-debug from rhel64

Comment 6 Magnus Glantz 2013-09-29 11:17:17 UTC
Created attachment 804668 [details]
main.log from install - rhel64

Comment 7 Magnus Glantz 2013-09-29 11:17:42 UTC
Created attachment 804669 [details]
rpm -qa from my RHEL64 server

Comment 8 Magnus Glantz 2013-09-29 11:39:50 UTC
If it's not clear, I'm opening this bug as the installation instructions on the Katello wiki (https://fedorahosted.org/katello/wiki/Install) states that Fedora 18 is the Fedora version to use with Katello.

Comment 9 Håkan Hagenrud 2013-10-14 13:15:29 UTC
I have the exact same issue, followed the instructions on the wiki.

F18 fresh install in VMware env
Do katello-configure --user-pass=XXXXXX
Gets an error in the log file about dependencies, "qpid-cpp-client-ssl","qpid-cpp-server-ssl".
Runing yum install "qpid-cpp-client-ssl","qpid-cpp-server-ssl" gets this result:
Package qpid-cpp-client-ssl-0.18-6.fc18.x86_64 is obsoleted by qpid-cpp-client-0.24-3.fc18.1.x86_64 which is already installed
Package qpid-cpp-server-ssl-0.18-6.fc18.x86_64 is obsoleted by qpid-cpp-server-0.24-3.fc18.1.x86_64 which is already installed
SO I edit the install.pp file and remove the dependency to qpid-cpp-server-ssl and qpid-cpp-client-ssl.
Also edit service.pp file to require qpid-cpp-server instead. Next I end up where Magnus was.

katello does not configure correctly and does not start.

Comment 10 Håkan Hagenrud 2013-10-14 13:33:37 UTC
Created attachment 812017 [details]
My debug package from fedora 18

Comment 11 Bryan Kearney 2014-01-21 19:07:16 UTC
Moving to Sat6 to be tracked there. Upstream bugs are moving to redmine.

Comment 12 RHEL Program Management 2014-01-21 19:19:12 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 14 Bryan Kearney 2014-01-21 20:07:43 UTC
I am not seeing this issue on installs.

Comment 16 Mike McCune 2014-05-05 17:23:55 UTC
CLOSED, not needing specific testing


Note You need to log in before you can comment on or make changes to this bug.