[Satellite6] What data to provide for pulp repo sync issues?

Environment

• Red Hat Satellite 6.9 or older

Issue

• Having a problem with either:
  • Repository sync
  • Capsule sync
  • Content View promote or publish

What additional data (together with sosreport and/or foreman-debug) are required for faster investigation of the customer problem?

Resolution

• all /var/log/messages* (data not required if Satellite runs on RHEL7 and wasn't rebooted since the event and sosreport is provided)
• several mongo collections:

echo "DBQuery.shellBatchSize = 10000000" > .mongorc.js

for i in repo_publish_results repo_sync_results task_status; do mongo pulp_database --eval "load('.mongorc.js'); db.${i}.find().shellPrint()" | gzip > ${i}.txt.gz; echo ${i}.txt.gz; done

(and provide the 3 files printed to standard output)

• for investigation of performance-related issues on Satellite 6.1 or older, complete task export:

foreman-rake foreman_tasks:export_tasks tasks=all days=5

(ensure "days=5" fully covers the time period of the problematic task(s))

For more KB articles/solutions related to Red Hat Satellite 6.x Pulp 2.0 Issues, please refer to the Consolidated Troubleshooting Article for Red Hat Satellite 6.x Pulp 2.0-related Issues

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.