Actions
Bug #19683
closedcontainer image repo synced to foreman-proxy-content loses pulp attribute repo_registry_id
Status:
Resolved
Priority:
Normal
Assignee:
Category:
Foreman Proxy Content
Target version:
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 ...
Updated by Thomas McKay over 7 years ago
- Blocks Tracker #19682: container image and registry tracker added
Updated by Thomas McKay over 7 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
Updated by Justin Sherrill over 7 years ago
- Translation missing: en.field_release set to 258
Updated by Justin Sherrill over 7 years ago
- Assignee changed from Thomas McKay to Justin Sherrill
- Target version changed from 195 to 202
Updated by Justin Sherrill over 7 years ago
- Assignee changed from Justin Sherrill to Thomas McKay
Updated by Eric Helms over 7 years ago
- Translation missing: en.field_release changed from 258 to 267
Updated by Justin Sherrill over 7 years ago
- Translation missing: en.field_release changed from 267 to 114
Updated by Justin Sherrill over 7 years ago
- Target version changed from 202 to 155
Updated by Thomas McKay over 6 years ago
- Status changed from Assigned to Resolved
This has been working for a couple releases
Actions