1.2. Known Issues

Known Issues and workarounds with Red Hat Satellite 6.0.
Report a bug

1.2.1. Installer

BZ#1139806 Satellite Server Host System Requires Update Before Satellite Installation

Make sure that the host system is fully updated before installing Red Hat Satellite. Attempts to install on host systems running Red Hat Enterprise Linux that are not fully updated may lead to difficulty in troubleshooting, as well as unpredictable results.

BZ#1125241 Initial Organizations or Locations Cannot Be Specified

Changes in the katello-installer resulted in a broken initial user seed data which prevents organization and location creation through the katello-installer command during installation. The initial organization and location are currently automatically generated as "Default Organization" and "Default Location" respectively. To create your own organization and location, log in to Satellite Server user interface and click on Administer → Users and Administer → Organizations.

BZ#1119910 Services fail to start during installation

Services failing to start and permissions being denied while installing Red Hat Satellite Server maybe attributed to restrictive umask permissions. Make sure that the root user's umask is set to 0022 before running katello-installer: 

# umask 0022
BZ#1124553 Specifying an Alternate Installation Directory Fails

Specifying alternate deployment directories with katello-installer at installation time is currently unsupported. Do not use the following options: 

    --certs-log-dir               When the log files should go (default: "/var/log/certs")
    --certs-password-file-dir     The location to store password files (default: "certs::params::password_file_dir")
    --certs-pki-dir               The PKI directory under which to place certs (default: "/etc/pki/katello")
    --certs-ssl-build-dir         The directory where SSL keys, certs and RPMs will be generated (default: "/root/ssl-build")
    --foreman-app-root            Name of foreman root directory (default: "/usr/share/foreman")
    --foreman-puppet-home         Puppet home directory (default: "/var/lib/puppet")
    --katello-config-dir          Location for Katello config files (default: "/etc/foreman/plugins")
    --katello-log-dir             Location for Katello log files to be placed (default: "/var/log/foreman/plugins")
BZ#1127307 Installer Fails When The Satellite Server Hostname Has A Hyphen

When the Satellite Server's hostname contains hyphens, the installation fails with errors. This issue occurs when the domain has no Top Level Domain (TLD). System administrators should make sure that the Satellite Server's hostname includes the TLD. For example: 

	Hostname without TLD: hostname.domain-example
	Hostname with TLD: hostname.domain-example.com

Note

Specifying a valid email address with a top level domain while configuring the Satellite Server will also work. For example: 
# katello-installer --foreman-admin-email=root@localhost.example.com
BZ#1122623 Installation Fails When Webserver Fails To Start

The installation fails with the error: 

Could not start Service[httpd]: Execution of '/usr/share/katello-installer/modules/service_wait/bin/service-wait httpd start' returned 1: Starting httpd: [Tue Jul 22 12:49:31 2014] [warn] module passenger_module is already loaded, skipping
/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]
This error occurs when puppet has been run on the host prior to the installation. This can occur in environments where the normal bootstrap process on the system involves running puppet. Because puppet has already generated the host pem files, puppet will not generate the ca cert when the installer runs. To work around this issue:
  1. Delete or move all of the contents of /var/lib/puppet/ssl.
  2. Generate a puppet certificate for the host system: 
    # puppet cert generate $(hostname -f)
  3. Clear all subsequent backend data stores: 
    # katello-installer --reset

Warning

This reset option will drop the database, all previous data will be lost. This should only be done prior to initial installation when there is no previous data accumulated. If there is any data you wish to be preserved, do not run the --reset option.
BZ#1121974 katello-installer Does Not Update Network Service Configuration Information for Capsule Servers

Running katello-installer after the initial configuration to enable the Capsule Server's TFTP, DNS and DHCP with the DNS and DHCP arguments, does not update the network service configuration. There is currently an issue with repeatedly running katello-installer that removes the dhcp/tftp settings. There are two options to update these settings after the initial configuration:

  • Run katello-installer with no arguments.
  • Edit the answer file /etc/katello-installer/answers.katello-installer.yaml with the new configuration options required.
BZ#1125414 Red Hat Satellite Server Default Admin Password Overwrites Any Password Changes Upon Subsequent Reruns of katello-installer

Subsequent reruns of the katello-installer command will change the admin password back to the default admin password regardless of any changes made through the web user interface. If you need to run katello-installer after changing your administrative password, login to the web user interace after running the katello-installer command with the default admin password to change it back to your preferred password.

Information about default passwords and how to reset your password back to the default one can be found in the Red Hat Satellite User Guide.
Report a bug