Issue

If a capsule is physically removed or unresponsive, outside of Satellite 6 itself, creation of repositories may hang indefinitely. The solution for this is to resolve the situation with the unresponsive capsule, removing it from the list of available capsules, if necessary.

The issue is the Satellite thinks the Capsule should be online and available but in situations where it is not (network failure, hardware issue, etc) the Satellite doesn't properly handle this situation with a clear outcome.
Users are left waiting for common operations to complete if the Capsule is offline.

There is a failure to synchronize repositories, pulp stays in the suspended mode.
The following error message shows up in the logs :

Actions::Pulp::Consumer::SyncNode (suspended)