Bug 2117289

Summary:	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
Product:	Red Hat Satellite	Reporter:	Satyajit Das <sadas>
Component:	Upgrades	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED MIGRATED	QA Contact:	Satellite QE Team <sat-qe-bz-list>
Severity:	medium	Docs Contact:
Priority:	high
Version:	6.11.0	CC:	ahumbe, amahindr, aruzicka, egolov, ehelms, ekohlvan, jalviso, lstejska, pdwyer, rlavi, saydas
Target Milestone:	Unspecified	Keywords:	MigratedToJIRA, Triaged, Upgrades, WorkAround
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2024-06-06 12:25:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.