This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2280402 - Incorrect rubygem-foreman_maintain installed on Satellite which causes inability to see next versions for upgrading
Summary: Incorrect rubygem-foreman_maintain installed on Satellite which causes inabil...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: Unspecified
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-05-14 21:01 UTC by Benjamin Kielhold
Modified: 2024-06-06 17:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 17:39:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-25152 0 None Migrated None 2024-06-06 17:39:05 UTC
Red Hat Knowledge Base (Solution) 7059014 0 None None None 2024-05-14 21:42:28 UTC

Description Benjamin Kielhold 2024-05-14 21:01:13 UTC 
Description of problem:
-----------------------
Incorrect version of package, `rubygem-foreman_maintain` installed will provide the following output when executing, `satellite-maintain upgrade list-versions` on satellite server:

   Checking for new version of satellite-maintain...
   Nothing to update, can't find new version of satellite-maintain.


Version-Release number of selected component (if applicable):
-------------------------------------------------------------
rubygem-foreman_maintain (Not version specific, but specific to the requirements of the Satellite version)


How reproducible:
-----------------
100%


Steps to Reproduce:
-------------------
1. Have a Satellite on version X (6.12) needing to upgrade to version Y (6.13)
2. Have any version repository `satellite-maintenance-6.-for-rhel-8-x86_64-rpms` enabled Y+1 (6.14 | 6.15)
3. Execute `satellite-maintain upgrade list-versions` and rubygem-foreman_maintain will update to the highest available version
4. Execute `satellite-maintain upgrade list-versions` once more:

   Checking for new version of satellite-maintain...
   Nothing to update, can't find new version of satellite-maintain.


Actual results:
---------------

   Checking for new version of satellite-maintain...
   Nothing to update, can't find new version of satellite-maintain.

Expected results:
-----------------

   Proper version should be displayed. For Satellite 6.12: 6.12.z and 6.13 options should be present.


Work Around:
------------

 1. Understand the current version of Satellite and repositories enabled.

      # rpm -q satellite
      # subscription-manager repos --list-enabled

 2. Execute, `yum downgrade rubygem-foreman_maintain` if the current satellite repository version is enabled which provides the required rubygem-foreman_maintain version. 

 3. Execute `satellite-maintain upgrade list-versions` and verify proper output is presented.

 4. Follow the rest of the upgrade documentation.
Comment 1 Sayan Das 2024-05-16 08:53:12 UTC 
Related KBs:

Running "foreman-maintain upgrade list-versions" does not list version on Satellite 6 - Red Hat Customer Portal
https://access.redhat.com/solutions/4330451

Execution of "satellite-maintain self-upgrade" fails with "Error getting repository data for rhel-7-server-satellite-maintenance-6.10.8-rpms" message in Red Hat Capsule 6.10 - Red Hat Customer Portal
https://access.redhat.com/solutions/6987559

The 'satellite-maintain upgrade list-versions' command does not show next upgradable version in Red Hat Satellite 6 - Red Hat Customer Portal
https://access.redhat.com/solutions/3497291

Unable to list Red Hat Satellite server version 6.11 for performing an upgrade of the Satellite server. - Red Hat Customer Portal
https://access.redhat.com/solutions/6974434

Red Hat Satellite server version 6.12 is not available for performing an upgrade of the Satellite server. - Red Hat Customer Portal
https://access.redhat.com/solutions/6986053

The 'satellite-maintain upgrade list-versions' command does not show the next upgradable version in Red Hat Satellite 6.12 due to the incorrect version of rubygem-foreman_maintain package installed on the Satellite Server - Red Hat Customer Portal
https://access.redhat.com/solutions/7059014


Mostly, The issue is due to 

* Upgrade failed, The cause was fixed and then the upgrade was completed by executing installer manually but that leaves the /var/lib/foreman-maintain/data.yml  with existing data of incomplete upgrade stuff. 

* Wrong version of rubygem-foreman_maintain installed [ either due to having wrong maintenance repo enabled or wrong modules enabled ]


We now a days, mostly observe this due to second reason i.e. the end-user might have not updated the rubygem-foreman_maintain package or enabled a much higher version of satellite-maintenance repository and updated the package from there. So that manual effort needs to be converted into a self-upgrade type action [ which we do suggest for capsule upgrades i.e. satellite-maintain self-upgrade but not for satellite ]
Comment 2 Eric Helms 2024-06-06 17:39:07 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.