Bug 1463831
| Summary: | [RFE] katello-restore should offer an option --skip-pulp-content | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Paul Armstrong <parmstro> |
| Component: | Satellite Maintain | Assignee: | satellite6-bugs <satellite6-bugs> |
| Status: | CLOSED MIGRATED | QA Contact: | Satellite QE Team <sat-qe-bz-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.2.10 | CC: | ahumbe, anrussel, apatel, aupadhye, avnkumar, bbuckingham, bkearney, bmbouter, cfouant, chrobert, dalley, dkliban, dmoessne, egolov, ehelms, ggainey, jrichards2, kgaikwad, ldelouw, mkalyat, momran, mvanderw, pjasbuti, saydas, sfroemer, vijsingh |
| Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA, PrioBumpGSS, Reopened, Triaged |
| Target Release: | Unused | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-06-05 21:24:29 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: | |||
|
Description
Paul Armstrong
2017-06-21 20:31:43 UTC
Fixed in Upstream, should be in 6.4 How is this fixed upstream?! The attached Foreman Issue Tracker link is still open....
It's still not an option for the restore command in 6.4 (now "foreman-maintain restore", instead of katello-restore), which is what this bug was all about. You can use the option with the backup command ("foreman-maintain backup [offline/online]"), but there's no way to do a restore with the pulp content missing.
Can this please be re-opened and addressed in a future update?
It would be really nice to be able to not have to store all the pulp RPM content on disk in the backup (content which can easily be restoring by doing a sync with RH CDN).
The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you. 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. The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you. 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. Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/21240 has been resolved. *** Bug 2236242 has been marked as a duplicate of this bug. *** Hi All, For my part, the customer that kicked this off has long ago gone down another route. They are now using ansible automation to rebuild the configuration from code. They lose some history from Satellite with this methodology, but it consistently gives them the desired config, optimizes storage, and provides allow for quickly creating systems for testing, etc.. For my customer, there is no longer a requirement for this RFE. Regards, Paul That would be a neat feature too. Maybe satellite could auto-generate a script/playbook which reproduces the setup. Please see: http://github.com/redhat-cop/rhis-builder This is the builder code. We need hammer or similar to ouput the yaml consumed by this project. This should be a separate RFE. I have texted back and forth with Eric previously. 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. Based upon feedback during auto-closure, leaving this bugzilla open a while longer for additional investigation; however, it may be closed in a future iteration. 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. |