Capsule synchronization failed with error "Action not allowed for the default capsule"

Environment

• Red Hat Satellite v 6.2
• Red Hat Capsule v 6.2

Issue

• Capsule synchronization failed with below error.

# hammer capsule content synchronize --name capsule.example.com
Could not synchronize capsule content:
  Action not allowed for the default capsule.

Resolution

• On the Capsule server,
  • Edit the file /etc/foreman-proxy/settings.d/pulp.yaml.
  • Change the :enabled: from https to false.

# cat /etc/foreman-proxy/settings.d/pulp.yml 
---
# Pulp integration
:enabled: false
<snipped>

• Restart the foreman-proxy service on Capsule server.

# service foreman-proxy restart

• On the Satellite Server,
  • Refresh the Capsule features.

# hammer capsule refresh-features --name capsule-server.example.com

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

Root Cause

• This is a known Bugzilla. This content is not included.Bug 1371085 - Confusing Capsules with feature pulp and pulp-node.
• To know that status of the Bugzilla, please contact the Red Hat Technical Support.

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.