Bug #19683
closed
container image repo synced to foreman-proxy-content loses pulp attribute repo_registry_id
Added by Thomas McKay over 7 years ago.
Updated over 6 years ago.
Category:
Foreman Proxy Content
|
Description
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
...
Related issues
1 (1 open — 0 closed)
<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
- Translation missing: en.field_release set to 258
- Status changed from New to Assigned
- Target version changed from 194 to 195
- Bugzilla link set to 1464183
- Assignee changed from Thomas McKay to Justin Sherrill
- Target version changed from 195 to 202
- Assignee changed from Justin Sherrill to Thomas McKay
- Translation missing: en.field_release changed from 258 to 267
- Translation missing: en.field_release changed from 267 to 114
- Target version changed from 202 to 155
- Status changed from Assigned to Resolved
This has been working for a couple releases
Also available in: Atom
PDF