3.14. Pulp Issues
- BZ 1242631: Cancellation of node sync tasks not propagated to the agent/capsule
- Issue
Cancellation of node sync tasks is not propagated to the agent. As a result, the task on the parent has a state of canceled but continues to run on the agent/node. This means that Katello considers the task canceled when it was not. This prevents new tasks from running by the agent until the previous task finishes normally. This can result in a backlog of agent requests and tasks on the node.
WorkaroundNone at this time.
- BZ 1105673: Dependency issues running pulp-puppet-module-builder on non-Satellite 6 machine
- Issue
Creating puppet git repositories on other than Satellite 6 machines fails because of dependency issues and import errors.
WorkaroundTo use the
pulp-puppet-module-buildercommand on a separate system from the Satellite Server, subscribe the system to a Red Hat Satellite 6 server. This provides access to the extra packages required: pulp-puppet-module-builderpython-setuptools and python-pulp-puppet-common. Enable the Red Hat Satellite 6 repositories and install the packages:# yum install pulp-puppet-module-builder python-setuptools python-pulp-puppet-common
- BZ 1229322: database error: too much data for sort() with no index
- Issue
If you try to access a large number of Content Views or Product Views the page may not display correctly, and instead display only "Loading..." The following error can occur in the production log:
This error can occur if there are too many sync result entries for mongo to sort without an index.database error: too much data for sort() with no index. add an index or specify a smaller limitWorkaroundThis issue is being worked on upstream and a fix will be available in a future release. To work around this issue, you need to uncomment and modify the
repo_sync_historyoption in the/etc/pulp/server.conffile as follows:[data_reaping] repo_sync_history: 2
This changes the default repository synchronization history value of 60 days to two days, reducing the table size considerably. See the bugzilla comments for more detailed information. - BZ 1227920: Install applicable errata task missed reporting kernel packages
- Issue
If you install an errata that includes kernel updates, the kernel and kernel-devel packages are not reported as being installed.
WorkaroundTo work around this issue, you can review the Content Host's package profile to confirm that the expected packages have been updated. This issue is being worked on upstream and will be addressed in a future release.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.