Project

General

Profile

Actions

Bug #9364

closed

Install katello-deploy on Centos 7

Added by Bradley Corner about 9 years ago. Updated over 5 years ago.

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

Description

I was asked to submit a foreman-debug
Up to this point there were no errors on the output.
Followed the base installation instructions.

Launching installer with command: katello-installer

Running shell command: katello-installer
qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps://katello.myregisteredsite.com:5671' add exchange topic event --durable returned 1 instead of one of [0]
/Stage[main]/Certs::Candlepin/Exec[create candlepin qpid exchange]/returns: change from notrun to 0 failed: qpid-config --ssl-certificate /etc/pki/katello/certs/java-client.crt --ssl-key /etc/pki/katello/private/java-client.key -b 'amqps://katello.myregisteredsite.com:5671' add exchange topic event --durable 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_proxy::Register/Foreman_smartproxy[katello.myregisteredsite.com]: Failed to call refresh: Could not load data from https://katello.myregisteredsite.com
/Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[katello.myregisteredsite.com]: Could not load data from https://katello.myregisteredsite.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


Files

foreman-debug-XTRmo.tar.xz foreman-debug-XTRmo.tar.xz 215 KB Bradley Corner, 02/12/2015 04:58 PM
katello-installer.log katello-installer.log 1.14 MB Greg Rapp, 02/13/2015 02:55 PM

Related issues 1 (0 open1 closed)

Has duplicate Katello - Bug #9243: katello-installer failing on RHEL-7DuplicateEric Helms02/05/2015Actions
Actions #1

Updated by Stephen Benjamin about 9 years ago

It looks like a problem with qpidd, and you're hitting https://bugzilla.redhat.com/show_bug.cgi?id=1130086.

Feb  8 14:28:51 katello python: SELinux is preventing /usr/sbin/qpidd from read access on the file .
If you believe that qpidd should be allowed read access on the  file by default.
# grep qpidd /var/log/audit/audit.log | audit2allow -M mypol

katello-deploy current does setenforce 0 (2.1.1 should have selinux support), but it seems like it's not working? Could you maybe try this:

  1. katello-service stop
  2. setenforce 0
  3. katello-installer
Actions #2

Updated by Greg Rapp about 9 years ago

I'm running into what appears to be the same problem installing 2.1 on a fresh copy of CentOS 7 with all updates applied and SELinux disabled. I've attached my installer log.

Actions #3

Updated by Bradley Corner about 9 years ago

Ran with your suggestions:
Installing Notice: /Stage[main]/Certs::Foreman/Exec[foreman_c [99%] /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[katello.myregisteredsite.com]: Could not evaluate: Could not load data from https://katello.myregisteredsite.com

Actions #4

Updated by Eric Helms about 9 years ago

  • Triaged changed from No to Yes
Actions #5

Updated by Eric Helms about 9 years ago

  • Has duplicate Bug #9243: katello-installer failing on RHEL-7 added
Actions #6

Updated by Eric Helms about 9 years ago

  • Assignee set to Eric Helms
  • Target version set to 66

Testing this patch for this issue -- https://github.com/Katello/puppet-service_wait/pull/8

Actions #7

Updated by The Foreman Bot about 9 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello-installer/pull/179 added
  • Pull request deleted ()
Actions #8

Updated by Bryan Kearney about 9 years ago

  • Bugzilla link set to 1193584
Actions #9

Updated by Eric Helms about 9 years ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100
Actions

Also available in: Atom PDF