The 'repo_registry_id' field on a pulp repo is not set when it is synced to a foreman-proxy-content capsule.
To confirm, use pulp-admin to examine the repo on both foreman and the capsule. Note that the repo registry id info should be present in both.
pulp-admin -u admin -p admin docker repo list --repo-id 3-rhcc-v2_0-00feb0ad-cfa1-4d6b-bc1b-367c0b777fe3 --details
Auto Publish: True
Created from redmine issue http://projects.theforeman.org/issues/19683
Upstream bug assigned to firstname.lastname@example.org
This was investigated upstream and it didn't seem to make much sense, as the Library instances are the only ones that have this special 'repo_registry_id'.
Content view instances such as the one in the description will never have a simple id. Closing for now, but feel free to reopen.