container image repo synced to foreman-proxy-content loses pulp attribute repo_registry_id
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 ... Distributors: Auto Publish: True Config: Protected: False Repo-registry-id: examplecorp-rhcc-2_0-red_hat_container_catalog-openshift3_ ose-docker-registry ...
#2 Updated by Thomas McKay about 5 years ago
<jsherrill> i bet we aren't propagating container_repository_name to repositories when we clone them for a CV
<jsherrill> thomasmckay: look at the build_clone method in repository.rb
<jsherrill> i think we need to add it there
<jsherrill> to copy the container_repository_name attribute