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:
foreman-maintain self-upgrade command added in BZ 2026415 for updating rubygem-foreman_maintain from next stream
When passing x.y version as target-version to self-upgrade it fails with comparing to satellite version, like for 6.10.1.1
# foreman-maintain self-upgrade --target-version 6.10
The target-version 6.10 should be greater than existing version 6.10.1.1!
Version-Release number of selected component (if applicable):
rubygem-foreman_maintain-1.0.1-1.el7sat.noarch
How reproducible:
always
Steps to Reproduce:
1. foreman-maintain self-upgrade --target-version 6.10
Actual results:
The target-version x.y should be greater than the existing version x.y.z!
Expected results:
If provide x.y version self-upgrade should pull from the latest x.y.z version
Additional info:
Hello Gaurav,
The self-upgrade command is meant for major version upgrades only and for .z stream upgrades users should go by the existing workflow where self upgrade of foreman-maintain package happens automatically from .z stream repo.
The command help text mentions this as well,
subcommand 'self-upgrade', 'Perform major version self upgrade',
https://github.com/theforeman/foreman_maintain/blob/894e362be977ef6db5bcb9db76198a864b759206/lib/foreman_maintain/cli.rb#L31
As per this should I close this bugzilla?
Regards,
Amit Upadhye.
Verified.
Tested on Satellite 6.11.0 Snap 15.0
Version: rubygem-foreman_maintain-1.0.6-1.el7sat.noarch
Steps:
1. # foreman-maintain self-upgrade --target-version 6.11/6.10
Observation:
Updated failure message will be displayed if the same or a previous Sat version passed as target-version, such as
"The target-version 6.11 should be greater than existing version 6.11.0,
and self-upgrade should be used for major version upgrades only!"
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.11 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-2022:5498