Bug 1905734 - Satellite UI shows incorrect OS as RHEL Workstation for a RHEL Server
Summary: Satellite UI shows incorrect OS as RHEL Workstation for a RHEL Server
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Fact
Version: 6.8.0
Hardware: Unspecified
OS: Linux
high
high
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Radek Mynar
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-08 22:53 UTC by Ragesh
Modified: 2023-09-15 00:52 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-10-21 07:56:07 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1429033 0 high CLOSED Host provisioned with RHEL Workstation OS, after provisioning displayed as generic RedHat 7.3 2023-12-15 15:54:22 UTC

Description Ragesh 2020-12-08 22:53:39 UTC
Description of problem:
Client with RHEL Server OS is incorrectly shown as RHEL Workstation  

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

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:
~~~
From Satellite:
# hammer host info --name xxx.xyz.com | grep Operating
Operating system:         
Operating System:       RHEL Workstation 7.6. 

From the client:
# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.6 (Maipo)

# subscription-manager facts | grep distribution.version
1:distribution.version: 7.6
2:distribution.version.modifier: ga
3:Exit status: 0

# subscription-manager facts | grep distribution.name
  distribution.name: Red Hat Enterprise Linux Server
~~~

Expected results:
Correct Operating system should be reflected. 
In this case RHEL Server 7.6

Additional info:
New BZ case opened as suggested in the following Bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1429033

Comment 1 Paul Dudley 2020-12-09 14:56:38 UTC
It should be noted in this particular case that ignore_facts_for_operatingsystem is set to false

Comment 2 Dwayne 2020-12-09 15:17:06 UTC
Set the Customer Escalation Flag = Yes to increase awareness, also EN-36308

Comment 7 Marek Hulan 2021-01-04 08:42:01 UTC
Thanks for provided data. The problem may not be that the server is detected as a workstation. The OS may not be updated by facts at all. As I mentioned in the original comment https://bugzilla.redhat.com/show_bug.cgi?id=1429033#c53, the OS name should either be RedHat_Workstation or RedHat if it's updated based on facts.

1) how did you create this host? using subscription-manager registration or by provisioning?
2) how was the OS created?
3) how was the OS assigned to the host e.g. at what step?
4) what facts exist for this host, e.g. `hammer fact list --search "host=xxx.xyz.com"`
5) is puppet agent running on this machine?
6) what does `hammer os list` show? can you provide `hammer os info --title "RHEL Workstation 7.6"`? we need to figure if it's the correct OS, the title can be masked by the description
7) if you manually change the OS, does it get reassigned back to the wrong value?

Comment 11 Ragesh 2021-01-04 19:50:58 UTC
Hello Marek,

Below are the answers to the questions:

1) how did you create this host? using subscription-manager registration or by provisioning?

Using provisioning.

2) how was the OS created?

Hosts are provisioned by foreman-discovery using provisioning templates.

3) how was the OS assigned to the host e.g. at what step?

As part of the foreman-discovery installation using provisioning templates.

4) what facts exist for this host, e.g. `hammer fact list --search "host=xxx.xyz.com"`

Note the actual host name changed to xxx.xyz.com in below output 

 hammer fact list --search "xxx.xyz.com"
-------------------------|----------------------------|-------------------------
HOST                     | FACT                       | VALUE                   
-------------------------|----------------------------|-------------------------
xxx.xyz.com              | network::hostname-override | xxx.xyz.com
xxx.xyz.com              | uname::nodename            | xxx.xyz.com
xxx.xyz.com              | networking::fqdn           | xxx.xyz.com
xxx.xyz.com              | fqdn                       | xxx.xyz.com
xxx.xyz.com              | network::fqdn              | xxx.xyz.com
xxx.xyz.com              | network::hostname          | xxx.xyz.com
-------------------------|----------------------------|-------------------------


5) is a puppet agent running on this machine?

Yes.


6) what does `hammer os list` show? can you provide `hammer os info --title "RHEL Workstation 7.6"`? we need to figure if it's the correct OS, the title can be masked by the description


hammer os info --title "RHEL Workstation 7.6"
Id:                 43
Title:              RHEL Workstation 7.6
Release name:       
Family:             Redhat
Name:               RedHat
Major version:      7
Minor version:      6
Partition tables:   
    Kickstart default
Default templates:  
    Kickstart default PXELinux (PXELinux)
    Kickstart default iPXE (iPXE)
    Discovery Red Hat kexec (kexec)
    Kickstart default (provision)
    Kickstart default user data (user_data)
    Kickstart default finish (finish)
Architectures:      
    x86_64
Installation media: 

Templates:          
    DEPRECATED Satellite Kickstart Default (provision)
    DEPRECATED Satellite Kickstart Default Finish (finish)
    DEPRECATED Satellite Kickstart Default User Data (user_data)
    Discovery Red Hat kexec (kexec)
    Kickstart default (provision)
    Kickstart default finish (finish)
    Kickstart default iPXE (iPXE)
    Kickstart default PXELinux (PXELinux)
    Kickstart default user data (user_data)
Parameters:

7) if you manually change the OS, does it get reassigned back to the wrong value?"

Yes, it get reassigned back to the wrong value

Regards,
Ragesh

Comment 13 Marek Hulan 2021-01-08 10:44:20 UTC
Thanks for the answers, it didn't reveal what I was hoping for, but gives me some leads. One follow-up question - in question 4) you provided only 6 facts, is that all you see? There should be more information, namely about OS. If there's more, please upload all of them.

Could you also please get the production.log with SQL logger enabled and log level set to debug? See https://access.redhat.com/solutions/1155573 for instructions how to do that. Please capture the production.log from the moment you change the OS to RHEL Server and until it gets switched back to RHEL Workstation. Also please upload output of `facter` from this RHEL machine.

As a quick workaround - you can tweak the setting so the OS is not updated based on facts, however I assume you want OSes to be correctly updated by facts and we'll try to find out, why in your case the wrong OS is associated.

Comment 16 Marek Hulan 2021-01-12 08:57:46 UTC
This is very suspicious, there should be many more facts, can you please also send what you see in Settings -> Puppet -> "Exclude pattern for facts stored in satellite"? Also we need the production.log with SQL logs on debug log level to move further.

Comment 18 Ragesh 2021-01-18 16:19:57 UTC
Hello Marek,
Please find below exclude pattern for facts:
[ lo, en*v*, vnet*, macvtap*, _vdsmdummy_, veth*, tap*, qvb*, qvo*, blockdevice*, mountpoints*, partitions* ]

Regards,
Ragesh K

Comment 34 Red Hat Bugzilla 2023-09-15 00:52:43 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days


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