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:
Installer fails to install new packages as it tries to use 

foreman-maintain packages is-locked --asumeyes
which no longer exists in the FM package:
# foreman-maintain packages is-locked --help
Usage:
    foreman-maintain packages is-locked [OPTIONS]

Options:
    -h, --help                    print help


We also found out, this has been present in Snap 9 too (rubygem-foreman_maintain-0.8.6-1.el7sat.noarch.rpm)

this got introduced by 0.8.3:
https://github.com/theforeman/foreman_maintain/pull/490/files

the change does not comply with what the related issues expects:
https://projects.theforeman.org/issues/30094 (it explicitly states assumeyes option for the is-locked subcommand).

Version-Release number of selected component (if applicable):
6.10.0 snap9+

Steps to Reproduce:
1. try to e.g. enable dhcp smart proxy using installer (it wil ltry to install some additional packages)
2. observe the failure

Actual results:


Expected results:


Additional info:

This should be fixed in foreman-maintain because otherwise we need to cherry pick it to all Satellite versions, including EOL ones because it can affect upgrades.

workaround:

remove `--assumeyes` from the foreman-maintain command in

/usr/share/foreman-installer/hooks/pre_commit/09-version_locking.rb:2

Verified.

Tested on Satellite 6.10.0 Snap 12
Version: rubygem-foreman_maintain-0.8.10-1.el7sat.noarch

Steps:
1. foreman-maintain packages is-locked --help

Observation:
For `is-locked` subcommand, option --assumeyes/-y is added back, and the installer is working for lock/unlock packages again.

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