Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
To avoid any accidental removal of puppet content during and upgrade from Satellite 6.9 to 6.10, please include a check and non-auto-accept step (using -y) to acknowledge the removal of the puppet content from the Satellite.
Version-Release number of selected component (if applicable):
6.10
How reproducible:
n/a
Steps to Reproduce:
1.
2.
3.
Actual results:
Puppet content will be removed as a result of the pulp2 to pulp3 upgrade
Expected results:
The installer will present an acknowledgment for the removal of puppet content before removal that will not be acknowledged by the -y option
Additional info:
If the desire to keep the installer process truly automated, please include an additional flag for puppet content removal. Something like '--remove-puppet-content' would suffice.
To clarify, any puppet content that is in use is not deleted and hosts will continue to use the puppet modules after upgrade.
The only puppet content that will be deleted are puppet modules that are in a puppet repository in Library or are in an un-published content view version (such as an old version). None of this will be in direct use by hosts.
Verified.
Tested on Satellite 6.9.5 Snap 3.0
Version: rubygem-foreman_maintain-0.8.10-1.el7sat.noarch
Steps:
1. foreman-maintain upgrade check --target-version 6.10
OR
1. foreman-maintain health check --label warn-before-puppet-removal
Observation:
A new warning check is introduced while upgrading from 6.9.z to 6.10 for puppet content removal, which waits for acknowledgment if repos found with `--content-type puppet` and `--assumeyes` works with this check for uninterrupted upgrade.
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.10 Satellite Maintenance Release), 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-2021:4697