Bug 1973037
| Summary: | migration plan creates ERROR line of 24000 characters in production.log | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Matthias Dellweg <mdellweg> |
| Component: | Repositories | Assignee: | Ian Ballou <iballou> |
| Status: | CLOSED ERRATA | QA Contact: | Sam Bible <sbible> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.9.0 | CC: | apatel, bbuckingham, jsherril, kgaikwad, peter.vreman, sbible, zhunting |
| Target Milestone: | 6.9.8 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tfm-rubygem-katello-3.18.1.47-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-01-27 17:33:09 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1957813 | ||
|
Description
Matthias Dellweg
2021-06-17 07:29:23 UTC
Created redmine issue https://projects.theforeman.org/issues/32869 from this bug Upstream bug assigned to iballou Upstream bug assigned to iballou Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32869 has been resolved. Is there a specific reason that this did not make it into 6.9.7? Hi Peter, Thanks for reaching out. It appears that it was unintentionally missed. There is a keyword that was missing that resulted in it being omitted from one of the queries used during the Satellite 6.9.7 triage. Thanks for the confirmation that it was unintentional. Any plans to add it in 6.9.8 or is 6.9.7 the final 6.9 release that will be the start of pulp3 migrations now that 6.10 is GA? We do not currently have a 6.9.8 scheduled; however, if one is, this will certainly be a candidate. Sad to hear there is no 6.9.8 planned. I can think of at least 3 BZs that i have applied the fixes myself already to fix known issues in 6.9.7: - https://bugzilla.redhat.com/show_bug.cgi?id=2027786 - https://bugzilla.redhat.com/show_bug.cgi?id=2027784 - https://bugzilla.redhat.com/show_bug.cgi?id=2027367 It is very customer unfriendly to force customers to a long-during and risky pulp3 upgrade to get fixes for any non-pulp/non-content. As a customer in entreprise world that cannot afford the risks that pulp3 brings i would expect at least a longer maintenance for 6.9.x series. RedHat even has it officially documented it at https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html-single/upgrading_and_updating_red_hat_satellite/index#upgrade_paths that avoiding pulp3 upgrades is a supported path: ~~~ For future upgrades following Satellite 7.0, you will be required to upgrade the operating system from RHEL 7 to RHEL 8 on your Satellite Servers and Capsules. You can upgrade the operating system in-place or through a cloning process. The latter includes migration of all data, configuration, and synced content. NOTE If you are planning to avoid the upgrade from Pulp 2 to Pulp 3 and deploy a new Satellite 6.10 infrastructure due to the Pulp 3 changes instead, you might want to wait for Satellite 7.0 to deploy with RHEL 8 directly. ~~~ Hi Peter, I appreciate you reaching out. Please know that I wasn't saying that there would not be a 6.9.8, only that one hadn't been formally scheduled. We are working on plans for one and you'll see this bugzilla aligned to it very soon. Thanks for your understanding. Verified on 6.9.8 - 1 Steps to Reproduce: 1. perform a Pulp2 to Pulp3 migration 2. sudo grep pulp2_distributor_repository_ids /var/log/foreman/production.log Expected Results: No excessive printing of migration plan logs. Actual Results: No excessive printing of migration plan logs. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Satellite 6.9.8 Async Bug Fix Update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:0320 |