Filed under satellite6

Installation and configuration of Red Hat Satellite 6: tips, workarounds, fixes and links

This post is a work in progress. I will keep track of the issues that I ran into while installing and configuring Red Hat Satellite 6 on Enterprise Linux 7.

Satellite as single instance

Are you running Satellite as a single instance to do "everything"? Then enable its DHCP, DNS and TFTP capsules (smart proxies)!

Repo issue on content host

In case of repo issues on a content host, run yum clean all and yum update first, before debugging further.

New content view created

When you create a Content View, be patient and let your repositories sync first.

Red Hat Common repository

Remember to add the Red Hat Common repository to the Content View of your VMs.

Satellite 6.0 specific

Satellite + VMware + "Unlimited Guest Subscription"

How to register RHEV / VMWare guest systems to Red Hat Satellite v6 to use 'Red Hat Unlimited Guest Subscription' subscriptions? by Mario Gamboa

Missing repos on client

Created a Content View but the client isn't showing all the repositories that you added? On the client:

  1. list all available subscriptions and look for the missing one: subscription-manager list --available --all
  2. add the missing subscription using its Pool ID: subscription-manager attach --pool=1234567890
  3. verify the subscription has been added: subscription-manager list --available --consumed
  4. see issue #2

If the repositories for your Content View aren't added/enabled automatically with subscription-manager register --org="Your_Organization" --activationkey="Your_Activation_Key" and subscription-manager attach --auto, in the Satellite 6 web interface go to Content → Activation Keys. Select your activation key and list the subscriptions. Make sure the subscriptions for your non-Red Hat repositories are added to the activation key.

RHEL 5 machines installed with Satellite 6 can't "consume" custom repositories

yum fails with [Errno -3] Error performing checksum: this is caused by the SHA-256 checksums used by Pulp for the repository. yum shipped with RHEL 5 doesn't support SHA256 yet. You can get SHA256 support by installing python-hashlib. Unfortunately, this package is not included in the Kickstart repository so you can't simply include it in the @packages list of your Kickstart file.

  1. Disable all your custom repositories
  2. Enable the Red Hat repositories
  3. Install python-hashlib
  4. Enable the custom repositories again
  rhel_compatible = == 'Redhat' && != 'Fedora'
  os_major = @host.operatingsystem.major.to_i
  section_end = (rhel_compatible && os_major <= 5) ? '' : '%end'

# Workaround for RHEL5 yum's SHA-256 incompatibility
# see and
echo "Workaround for SHA256 incompatibility in RHEL5 yum"
subscription-manager repos --disable="*Default_Organization_*"
subscription-manager repos --enable="rhel-<%= @host.operatingsystem.major %>-*"
yum -y install python-hashlib
subscription-manager repos --enable="*Default_Organization_*"

Trying to publish new version of a Content View results in error Duplicate resource: Default_Organization-Example

This is a known bug and is supposed to be solved in Satellite 6.1, the fix won't be backported to 6.0. To fix the issue in Satellite 6.0, follow the steps from Mike McCune's post.

Failed to generate PXELinux template: private methodtemplate' called for nil:NilClass` when trying to cancel a build

This cryptic error is caused by a missing PXE template.

  1. In the Satellite 6 web interface go to Administer → Locations → Your Location → Templates and make sure that every template starting with "PXE" is added to your Location.
  2. Repeat the steps of #1 for Administer → Organization → Your Organization → Templates
  3. According to Foreman bug report #2215 "PXE Localboot Default" is enough, but it didn't fix my issue. When I enabled debugging in Foreman, I came by the query SELECT "config_templates".* FROM "config_templates" WHERE "config_templates"."id" IN (49, 46, 44, 14, 15, 1, 39, 47, 45, 41, 40, 35, 33, 34, 28, 36, 30, 37, 48) AND "config_templates"."name" = 'PXELinux default local boot' ORDER BY LIMIT 1. So the missing template that caused days of headache was actually called PXELinux default local boot

Can't start the celerybeat service

systemctl start pulp_celerybeat leads to:

celery: ERROR: Pidfile ( already exists.
celery: Seems we're already running? (pid: 1476)
celery: celery beat v3.1.11 (Cipater) is starting.
systemd: pulp_celerybeat.service: main process exited, code=exited, status=73/n/a
systemd: Unit pulp_celerybeat.service entered failed state.


The pid file is stored in /var/lib/pulp/celery/ Remove it and run systemctl start pulp_celerybeat.

Can't create a new host because the PTR record already exists

  1. Find the offending record in /var/named/dynamic/ and
  2. delete the PTR record with nsupdate:

    echo "server update delete PTR send " | nsupdate -k /etc/rndc.key

Can't execute any of the rpm subcommands with pulp-admin

Install the missing packages packages: yum install pulp-admin-client pulp-rpm-admin-extensions.noarch pulp-rpm-handlers.noarch as described in How to deploy and use pulp-admin.

Warning: The pulp-admin command can easily corrupt your database or put the pulp or katello databases out of sync. The use of pulp-admin outside the scope and direction of Red Hat Global Support Services is unsupported.

Remove all tasks in error state with foreman-rake console

ForemanTasks::Task.where(:result => :error).destroy_all. Change :result => :error to :state => :pending to remove pending tasks. See Red Hat KB solution #1381053.

Trying to change a host's Content View via fails with the message Katello::Resources::Candlepin::Consumer: 410 Gone {"displayMessage":"Unit xxx has been deleted","requestUuid":"yyy","deletedId":"xxx"} (GET /candlepin/consumers/xxx)

Remove the host from the Foreman Postgres database:

  1. su - postgres
  2. psql foreman
  3. foreman=# select id, name from katello_systems where name = '', note down the ID of the host
  4. foreman=# delete from katello_system_activation_keys where system_id = 123, 123 is the ID we got in the previous query
  5. foreman=# delete from katello_system_errata where system_id = 123;
  6. foreman=# delete from katello_systems where name = ''

Now you can update the Content View of the host.

Similar as above: to remove all hosts that use a Content View that's causing 410: Gone errors

  1. su - postgres
  2. psql foreman
  3. foreman=# select id, name from katello_content_views where name like '%content view%';, note down the ID of the host
  4. foreman=# delete from katello_system_activation_keys where (system_id) in (select id from katello_systems where content_view_id = 123);, 123 is the ID we got in the previous query
  5. foreman=# delete from katello_system_errata where (system_id) in (select id from katello_systems where content_view_id = 123);
  6. foreman=# delete from katello_system_repositories where (system_id) in (select id from katello_systems where content_view_id = 123);
  7. foreman=# delete from katello_systems where content_view = 123;

Search queries for Content Hosts view

content_view:"Your content view name" AND (environment:"your environment")

Satellite clients can't install packages because the URL in /etc/yum.repos.d/*.repo is incorrect

(Re-)run subscription-manager config --rhsm.baseurl= to correct the URL.

Tagged , , , , , , ,