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 2117289 - After a successful in-place upgrade of the satellite server to RHEL-9 using Leapp, Satellite GUI still shows the old/wrong Operating System version
Summary: After a successful in-place upgrade of the satellite server to RHEL-9 using L...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Upgrades
Version: 6.11.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Satellite QE Team
URL:
Whiteboard:
: 2254274 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-08-10 14:11 UTC by Satyajit Das
Modified: 2024-06-06 12:25 UTC (History)
11 users (show)

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

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-19269 0 None Migrated None 2024-06-06 12:25:47 UTC
Red Hat Knowledge Base (Solution) 6975245 0 None None None 2024-01-15 15:28:58 UTC

Description Satyajit Das 2022-08-10 14:11:59 UTC 
Description of problem:

After a successful in-place upgrade of the satellite server to Rhel-8 using Leapp, Satellite GUI still shows the old/wrong Operating System version( 7.9).

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

Satellite 6.11
Rhel 7.9 to Rhel 8.6 

How reproducible:

100%


Steps to Reproduce:

1. Followed the steps from the doc to upgrade the Satellite server from Red Hat Enterprise Linux 7 to Red Hat Enterprise Linux 8.

Chapter 4. Upgrading Satellite to Red Hat Enterprise Linux 8 In-Place Using Leapp
-------------------------------------------------------------------------------------------------------------
https://access.redhat.com/documentation/en-us/red_hat_satellite/6.11/html-single/upgrading_and_updating_red_hat_satellite/index#upgrading-project-in-place-using-leapp_upgrade-guide

2. upgrade to Rhel-8 was successful.

Actual results:

Satellite GUI still shows the old/wrong Operating System version( 7.9).

# hammer host info --name satellite.example.com
   Operating system:        
    Architecture:           x86_64
    Operating System:       RHEL Server 7.9  ==========================>  Still shows 7.9, as the backend DB is not updated with the latest OS facts.
    Build:                  no
    Custom partition table:

Expected results:

As the OS is successfully upgraded, OS facts for the satellite server should be updated in the Satellite GUI.

# subscription-manager release
Release: 8.6
# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.6 (Ootpa)

Additional info:

workaround:-

Manually update the Operating System version using the hammer:-

# hammer host update --name satellite.example.com  --operatingsystem "RedHat 8.6"
Comment 4 Ewoud Kohl van Wijngaarden 2024-01-25 14:03:36 UTC 
The installer ensures a host exists and uploads facts:

https://github.com/theforeman/puppet-foreman/blob/908ed638790f3cfc6e2f5f62e1b023c907a9913c/manifests/register.pp#L6-L15

The foreman_host provider only uses the facts on create, but doesn't update. https://github.com/theforeman/puppet-foreman/blob/master/lib/puppet/provider/foreman_host/rest_v3.rb could be enhanced to do so. leapp runs the installer, so I'd imagine it would solve the issue. My biggest concern is breaking other functionality, do that would need to be verified.
Comment 5 Griffin Sullivan 2024-01-25 15:19:21 UTC 
*** Bug 2254274 has been marked as a duplicate of this bug. ***
Comment 6 Eric Helms 2024-03-21 13:00:02 UTC 
This issue will be re-purposed to solve this for our RHEL 8 to RHEL 9 upgrades.
Comment 7 Eric Helms 2024-06-06 12:25:48 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.