Bug 1313502
| Summary: | [RFE] docker push functionality in Satellite 6 | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Nagoor Shaik <nshaik> |
| Component: | Container Management - Content | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.1.7 | CC: | ahogbin, ahumbe, amdas, bbuckingham, bkearney, bmidwood, dgross, dhill, fgarciad, ggainey, hyu, jsherril, ktordeur, mhrivnak, mkalyat, msunil, myarboro, mzalewsk, pcreech, rbertolj, rchan, rjerrido, rlavi, selvam_e2002, sgraessl, sputhenp, sraut, ttereshc, vijsingh |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA, PrioBumpGSS, Reopened, Triaged |
| Target Release: | Unused | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Enhancement | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-05 21:23:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
The Pulp upstream bug status is at MODIFIED. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. Relies on pulp-2.15 All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. The Pulp upstream bug status is at ON_QA. Updating the external tracker on this bug. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. The pulp feature associated with this is only a beginning step to functionality. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. https://pulp.plan.io/issues/2810 Unassociating pulp issue so bot stops flipping this to POST FWIW, if you link, for example, Foreman issue which is not complete, automation won't change status to POST. Connecting redmine issue http://projects.theforeman.org/issues/22301 from this bug Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/22301 has been resolved. *** Bug 1557101 has been marked as a duplicate of this bug. *** 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. created case with Redhat to reopen and add this feature in satellite. The Pulp upstream bug status is at CLOSED - CURRENTRELEASE. Updating the external tracker on this bug. The Pulp upstream bug priority is at Normal. Updating the external tracker on this bug. All upstream Pulp bugs are at MODIFIED+. Moving this bug to POST. 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 :) Created redmine issue https://projects.theforeman.org/issues/33901 from this bug 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. 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. *** Bug 1826564 has been marked as a duplicate of this bug. *** *** Bug 2107079 has been marked as a duplicate of this bug. *** 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. |
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