Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1464183 - container image repo synced to foreman-proxy-content loses pulp attribute repo_registry_id
Summary: container image repo synced to foreman-proxy-content loses pulp attribute rep...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Capsule - Content
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-22 15:11 UTC by Tom McKay
Modified: 2017-07-24 20:50 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-19 15:32:29 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19683 0 None None None 2017-06-22 15:11:09 UTC

Description Tom McKay 2017-06-22 15:11:06 UTC 
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.

<pre>

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
...
</pre>
Comment 1 Tom McKay 2017-06-22 15:11:11 UTC 
Created from redmine issue http://projects.theforeman.org/issues/19683
Comment 2 Tom McKay 2017-06-22 15:11:16 UTC 
Upstream bug assigned to tomckay
Comment 5 Justin Sherrill 2017-07-19 15:32:29 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.