This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 1446111 - [RFE] Allow a Satellite or Capsule to retrieve content from public RHUI instances
Summary: [RFE] Allow a Satellite or Capsule to retrieve content from public RHUI insta...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Repositories
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks: 2138220
TreeView+ depends on / blocked
 
Reported: 2017-04-27 09:43 UTC by Rich Jerrido
Modified: 2024-10-04 04:25 UTC (History)
21 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-05 21:24:24 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-15739 0 None Migrated None 2024-06-05 21:24:23 UTC

Description Rich Jerrido 2017-04-27 09:43:52 UTC 
Description of problem:

Typically, if I set up a new Pulp instance I can set up a local content source to help populate it quickly. However, if I am using EC2, I can't use my region's local RHUI to help populate my Pulp.

The content source config allows for most of what I need: the CA, client cert and client key. However, RHUI in EC2 requires additional metadata from the cloud-init magic IP in the HTTP header to allow the request through. These settings are specific to an instance, but do not generally change once the instance is created.

If there was a way to specify additional HTTP headers in the content request, it would be let Pulp users set up RHUI as an alternate content source. A very basic way to do this would be to allow setting arbitrary HTTP headers in the conf file.
Comment 1 pulp-infra@redhat.com 2017-04-27 12:37:04 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 2 pulp-infra@redhat.com 2017-04-27 12:37:06 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 3 Brad Buckingham 2017-04-28 18:03:21 UTC 
Placing this on Pulp component.  It can be moved back to Content Management, once the associated upstream pulp issue has been addressed.
Comment 4 pulp-infra@redhat.com 2017-05-08 20:37:17 UTC 
The Pulp upstream bug status is at ASSIGNED. Updating the external tracker on this bug.
Comment 5 pulp-infra@redhat.com 2017-05-11 20:07:47 UTC 
The Pulp upstream bug status is at POST. Updating the external tracker on this bug.
Comment 6 pulp-infra@redhat.com 2017-05-18 13:07:37 UTC 
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.
Comment 7 pulp-infra@redhat.com 2017-05-18 13:37:49 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 8 Michael Hrivnak 2017-07-24 07:32:55 UTC 
It looks like there are next steps at the Katello level to use the functionality in Pulp. I'm changing the component so you can pick that up.
Comment 9 pulp-infra@redhat.com 2017-07-31 14:50:49 UTC 
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.
Comment 10 pulp-infra@redhat.com 2017-08-15 14:35:51 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 18 Bryan Kearney 2018-09-28 19:14:02 UTC 
Moving this back to NEW until the RHUI side is completed.
Comment 19 pulp-infra@redhat.com 2018-09-28 19:39:39 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 24 pulp-infra@redhat.com 2019-07-26 22:36:03 UTC 
Requesting needsinfo from upstream developer bizhang because the 'FailedQA' flag is set.
Comment 26 pulp-infra@redhat.com 2019-09-04 17:07:01 UTC 
Requesting needsinfo from upstream developer bizhang because the 'FailedQA' flag is set.
Comment 27 pulp-infra@redhat.com 2019-09-04 18:06:42 UTC 
Requesting needsinfo from upstream developer bizhang because the 'FailedQA' flag is set.
Comment 28 pulp-infra@redhat.com 2019-10-28 13:46:15 UTC 
Requesting needsinfo from upstream developer bizhang because the 'FailedQA' flag is set.
Comment 29 pulp-infra@redhat.com 2019-11-18 14:37:17 UTC 
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.
Comment 31 pulp-infra@redhat.com 2020-05-27 21:04:08 UTC 
Requesting needsinfo from upstream developer dkliban, ttereshc because the 'FailedQA' flag is set.
Comment 32 pulp-infra@redhat.com 2020-10-05 14:48:34 UTC 
Requesting needsinfo from upstream developer bmbouter, ipanova because the 'FailedQA' flag is set.
Comment 33 pulp-infra@redhat.com 2020-10-05 16:30:39 UTC 
Requesting needsinfo from upstream developer bmbouter, ipanova because the 'FailedQA' flag is set.
Comment 34 Brian Bouterse 2020-10-05 18:24:06 UTC 
The automation keeps pinging pulp even though on IRC it's confirmed there is no pulp work to do. I've removed the upstream relationship as a workaround, here's the link to it for posterity:  https://pulp.plan.io/issues/1282
Comment 36 pulp-infra@redhat.com 2020-12-02 15:07:10 UTC 
The Pulp upstream bug status is at NEW. Updating the external tracker on this bug.
Comment 37 pulp-infra@redhat.com 2020-12-02 15:07:12 UTC 
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.
Comment 39 Mike McCune 2021-03-11 18:50:58 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in one month's time. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 42 Mike McCune 2021-06-08 21:14:27 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 43 Mike McCune 2021-07-13 21:54:48 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 46 Tanya Tereshchenko 2021-10-30 15:15:37 UTC 
This is just to confirm that it's being actively worked on in the upstream, see https://pulp.plan.io/issues/7832 to check progress.
Comment 47 pulp-infra@redhat.com 2021-11-10 08:13:54 UTC 
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.
Comment 48 pulp-infra@redhat.com 2021-11-10 09:10:34 UTC 
Requesting needsinfo from upstream developer ttereshc, ggainey because the 'FailedQA' flag is set.
Comment 63 Eric Helms 2024-06-05 21:24:24 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Comment 64 Red Hat Bugzilla 2024-10-04 04:25:02 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days
Note You need to log in before you can comment on or make changes to this bug.