Bug 1984898 - Installer fails to unlock packages using foreman-maintain
Summary: Installer fails to unlock packages using foreman-maintain
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Foreman Maintain
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: 6.10.0
Assignee: Amit Upadhye
QA Contact: Gaurav Talreja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-22 12:43 UTC by Roman Plevka
Modified: 2021-11-16 13:48 UTC (History)
6 users (show)

Fixed In Version: rubygem-foreman_maintain-0.8.9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 13:48:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 30094 0 Normal Closed Unnecessary options present in subcommands of "foreman-maintain packages" command. 2021-07-27 11:40:08 UTC
Red Hat Product Errata RHBA-2021:4697 0 None None None 2021-11-16 13:48:30 UTC

Description Roman Plevka 2021-07-22 12:43:45 UTC
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:

Comment 1 Ewoud Kohl van Wijngaarden 2021-07-22 15:26:26 UTC
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.

Comment 2 Roman Plevka 2021-07-22 15:30:40 UTC
workaround:

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

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

Comment 3 Gaurav Talreja 2021-08-12 08:13:58 UTC
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.

Comment 6 errata-xmlrpc 2021-11-16 13:48:19 UTC
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


Note You need to log in before you can comment on or make changes to this bug.