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:

Add an ability to force subscription-manager re-registration from the template. For mass registration it would be useful to have a flag to use subscription-manager --force to override those previously registered elsewhere. Or alternatively, an option to run “subscription-manager clean” first. 

While it is possible to edit the registration template globally, having the option in the host registration form allows for differentiate policies, and is more user-friendly. Forgetting to un-edit the template could lead to unwanted re-registrations, UI option supports a concious decision about it. 

The risk of overwriting the data should be clearly communicated

Created redmine issue https://projects.theforeman.org/issues/31820 from this bug

*** Bug 1919983 has been marked as a duplicate of this bug. ***

*** Bug 1919888 has been marked as a duplicate of this bug. ***

Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/31820 has been resolved.

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 (Moderate: Satellite 6.10 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/RHSA-2021:4702