Project

General

Profile

Bug #8869

operating system matching incorrect on RHEL Server/Client

Added by Adam Winberg over 4 years ago. Updated almost 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Inventory
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Running with unattended=false.

We have both RHEL Server and RHEL Client managed by puppet/foreman but the operatingsystem set for these is incorrect in many cases. If a new operatingsystem is added, say "RHEL Server 7.0", then this will be assigned to machines running "RHEL Client 7.0" as well.

My guess is that foreman matches only against name + major_version + minor_version which is the same for RHEL Server and RHEL Client. Right now all our RHEL7 Servers has the correct operatingsystem (RHEL Server 7.0) but foreman has not generated a new operatingsystem for Clients, it just uses the same as for Servers.

Not sure when this started, but i believe it happened when we upgraded from 1.5 to 1.6. We are now at 1.7.1.


Related issues

Related to Katello - Bug #6264: Allow selection of different kickstart variants and/or reposRejected

History

#1 Updated by Adam Winberg almost 4 years ago

Any feedback on this? The issue is still present (foreman 1.9.3), for example I updated some nodes to the RHEL7.2 Client beta a while ago, which created a new Operating System in foreman named "RHEL Client 7.2 Beta". Today I updated a server to RHEL7.2 (not beta) and the server also got assigned the "RHEL Client 7.2 Beta" Operating System in foreman, which is wrong.

Apart from getting the OS naming correct in foreman, it would also be nice to be able to manually edit OS names in foreman, even when using unattended.

#2 Updated by Michael Moll over 2 years ago

  • Related to Bug #6264: Allow selection of different kickstart variants and/or repos added

Also available in: Atom PDF