1.2.7. Content Management

BZ#1111574 Content Host API Calls Time Out

Red Hat Satellite 6 APIs that call on method "GET /katello/api/systems (DEPRECATED) List content hosts" may experience performance issues when there are over 300 hosts registered on the Satellite Server. A future release will address this issue.

BZ#1134594 Adding a Repository When a Satellite Capsule Server Is Missing Renders UI Non-Responsive Indefinitely

If a Satellite Capsule Server is physically removed or unresponsive, creating new repositories may hang indefnitely. Note that in cases where the Satellite Server and the Satellite Capsule Server are geographically far apart with slow or low bandwidth between the systems, it is possible that custom repository creation can take a significant amount of time.

There are two options to prevent this scenario from happening:
  • Restart the Satellite Capsule Server so that the Satellite Server can reconnect to it.
  • Remove the faulty Satellite Capsule Server from the Capsule Server list:
    1. Log in to the Red Hat Satellite Server.
    2. Click Infrastructure → Capsule and search for the faulty Satellite Capsule Server on the list.
    3. On the right-most column of the faulty Satellite Capsule Server, click on the drop-down menu and choose Delete. Click Ok to confirm deletion.
BZ#1122055 qpid Service Fails to Start After Promoting a Large Number of Content Views

When promoting a large number of content views and the qpid service fails with this operation error: 

Starting Qpid AMQP daemon: Daemon startup failed: Queue pulp.agent.5752dc04-7536-4e5c-b406-a0cd5d9c9119: recoverMessages() failed: jexception 0x0104 RecoveryManager::getFile() threw JERR__FILEIO: File read or write failure. (/var/lib/qpidd/qls/jrnl/pulp.agent.5752dc04-7536-4e5c-b406-a0cd5d9c9119/818fa4b0-3319-4478-b2b0-d2195f90f695.jrnl) (/builddir/build/BUILD/qpid-0.22/cpp/src/qpid/linearstore/MessageStoreImpl.cpp:1004)
This is caused by the Operating System limiting the number of file descriptors that qpid can use to read journal files when it starts. To prevent this issue, increase the ulimit on your Satellite Server host system.
BZ#1136213 Publishing Content Views Fail When Included Repositories Are Not Synchronized

When attempting to publish a Content View with unsynchronized repositories, the process fails with error "Could not find a published directory".

Ensure that all repositories have been enabled and synchronized prior to adding them to a Content View. A Content View cannot be published if the repositories have not been synchronized.
Report a bug