Project

General

Profile

Actions

Bug #7801

closed

katello-installer-2.0.1-1.el7 errors with defaults

Added by Pat Riehecky almost 10 years ago. Updated about 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Installer
Target version:
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

I followed the instructions at: http://www.katello.org/docs/installation/index.html for the 2.0 release for EL7

[root@testify]# katello-installer
Execution of '/bin/yum d 0 -e 0 -y list rubygem-katello' returned 1: Error: No matching Packages to list
/Stage[main]/Katello::Install/Package[rubygem-katello]/ensure: change from absent to present failed: Execution of '/bin/yum -d 0 -e 0 -y list rubygem-katello' returned 1: Error: No matching Packages to list
/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]/Candlepin::Service/Exec[cpinit]: Failed to call refresh: /usr/bin/wget --timeout=30 --tries=5 --retry-connrefused -qO
http://localhost:8080/candlepin/admin/init >/var/log/candlepin/cpinit.log 2>&1 && touch /var/lib/candlepin/cpinit_done returned 4 instead of one of [0]
/Stage[main]/Candlepin::Service/Exec[cpinit]: /usr/bin/wget --timeout=30 --tries=5 --retry-connrefused qO http://localhost:8080/candlepin/admin/init >/var/log/candlepin/cpinit.log 2>&1 && touch /var/lib/candlepin/cpinit_done returned 4 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]/Exec[foreman-rake-apipie:cache]: Failed to call refresh: /usr/sbin/foreman-rake apipie:cache returned 1 instead of one of [0]
/Stage[main]/Foreman::Database/Foreman::Rake[apipie:cache]/Exec[foreman-rake-apipie:cache]: /usr/sbin/foreman-rake apipie:cache returned 1 instead of one of [0]
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[testify.fnal.gov]: Failed to call refresh: Could not load data from https://testify.fnal.gov
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[testify.fnal.gov]: Could not load data from https://testify.fnal.gov
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

I've attached the katello-installer log with xz compression.

The host system runs SL 7.0


Files

katello-installer.log.xz katello-installer.log.xz 71.5 KB katello-installer.log from testify Pat Riehecky, 10/02/2014 04:51 PM
Actions #1

Updated by Eric Helms almost 10 years ago

  • Status changed from New to Need more information
  • Translation missing: en.field_release set to 24
  • Triaged changed from No to Yes

Do you have system proxy settings set? (i.e. http_proxy=http://foo.com)

Actions #2

Updated by Pat Riehecky almost 10 years ago

There are no proxy settings configured.

The system itself is a default installation with a good connection to the internet. No proxys are required for any outbound traffic.

Actions #3

Updated by Eric Helms over 9 years ago

  • Translation missing: en.field_release changed from 24 to 14
Actions #4

Updated by Eric Helms over 9 years ago

Are you still hitting this issue?

Actions #5

Updated by Pat Riehecky over 9 years ago

I've not checked recently.

Do you want me to try with 2.0 or 2.1?

Pat

Actions #6

Updated by Eric Helms over 9 years ago

If you can re-try with 2.0 since 2.1 is not out yet that'd be great. I have not seen or heard other users report this issue so would like to address or close it out.

Actions #7

Updated by Pat Riehecky over 9 years ago

I've gotten past the previous bug, but it doesn't look like the fix from #7882 is in the 2.0 codebase so I can't call it a success......

Actions #8

Updated by Eric Helms over 9 years ago

  • Status changed from Need more information to Closed
  • Target version set to 62
Actions

Also available in: Atom PDF