Bug 1313502 - [RFE] docker push functionality in Satellite 6
Summary: [RFE] docker push functionality in Satellite 6
Keywords:
Status: NEW
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management - Content
Version: 6.1.7
Hardware: All
OS: Linux
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 1557101 1826564 2107079 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-01 17:34 UTC by Nagoor Shaik
Modified: 2024-04-04 16:28 UTC (History)
30 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-18 19:44:22 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 33901 0 High New docker push functionality in katello 2021-11-10 16:46:41 UTC
Red Hat Knowledge Base (Solution) 3376451 0 None None None 2018-03-19 16:51:16 UTC
Red Hat Knowledge Base (Solution) 3459551 0 None None None 2023-07-17 20:03:41 UTC
Red Hat Knowledge Base (Solution) 4175551 0 None None None 2019-05-28 05:29:05 UTC

Internal Links: 1671456

Comment 2 Tom McKay 2017-10-27 13:40:46 UTC
Docker Image Registry in Satellite
      
2. What is the nature and description of the request?  
We want to store all custom build images inside RedHat Satellite, so we can have a single Rep for all Services.
      
3. Why do you need this? (List the business requirements here)
Same as 2

4. How would you like to achieve this? (List the functional requirements here)  
With the native docker commands like "docker push", "docker pull"
 
5. For each functional requirement listed, specify how Red Hat and you can  test to confirm the requirement is successfully implemented.  

Yes using the docker pull or docker push commands

6. Does you have any specific timeline dependencies and which release would they like to target (i.e. RHEL6, RHEL7)?  
No

Comment 3 pulp-infra@redhat.com 2017-10-27 14:02:09 UTC
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug.

Comment 4 pulp-infra@redhat.com 2017-10-27 14:02:12 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 5 Tom McKay 2017-10-27 14:22:13 UTC
Relies on pulp-2.15

Comment 6 pulp-infra@redhat.com 2017-10-27 14:32:28 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 7 pulp-infra@redhat.com 2017-11-30 18:33:05 UTC
The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug.

Comment 8 pulp-infra@redhat.com 2018-01-17 21:32:36 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 9 Tom McKay 2018-01-22 12:50:55 UTC
The pulp feature associated with this is only a beginning step to functionality.

Comment 10 pulp-infra@redhat.com 2018-01-22 13:02:22 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 11 Tom McKay 2018-01-31 11:56:56 UTC
https://pulp.plan.io/issues/2810

Unassociating pulp issue so bot stops flipping this to POST

Comment 12 Tanya Tereshchenko 2018-01-31 14:24:02 UTC
FWIW, if you link, for example, Foreman issue which is not complete, automation won't change status to POST.

Comment 13 Tom McKay 2018-02-14 12:44:20 UTC
Connecting redmine issue http://projects.theforeman.org/issues/22301 from this bug

Comment 14 Satellite Program 2018-02-22 15:03:55 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22301 has been resolved.

Comment 15 Brad Buckingham 2018-03-19 16:51:16 UTC
*** Bug 1557101 has been marked as a duplicate of this bug. ***

Comment 33 Bryan Kearney 2020-05-22 14:51:22 UTC
Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.

Comment 34 selvam 2020-05-28 07:42:29 UTC
created case with Redhat to reopen and add this feature in satellite.

Comment 37 pulp-infra@redhat.com 2021-10-12 14:11:15 UTC
The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug.

Comment 38 pulp-infra@redhat.com 2021-10-12 14:11:17 UTC
The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug.

Comment 39 pulp-infra@redhat.com 2021-10-12 15:11:50 UTC
All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST.

Comment 40 Justin Sherrill 2021-11-10 16:18:44 UTC
There is still work needed in katello for this, but this keep getting flipped back to POST due to the pulp issue.  Removing the new pulp issue again :)

Comment 41 Justin Sherrill 2021-11-10 16:46:39 UTC
Created redmine issue https://projects.theforeman.org/issues/33901 from this bug

Comment 42 Mike McCune 2022-01-28 22:33:49 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 45 Mike McCune 2022-03-18 19:44:22 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.

Comment 55 Ian Ballou 2022-11-09 14:40:42 UTC
*** Bug 1826564 has been marked as a duplicate of this bug. ***

Comment 60 Samir Jha 2023-12-19 14:48:56 UTC
*** Bug 2107079 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.