Bug #6006
closedOS facts should not overwrite the OS selected to provision with
Description
Migrated from https://github.com/theforeman/foreman/issues/1489
We setup a specific Operatingsystem, 'Ubuntu 12.04 + 3.2.0-59 kernel', and selected this OS in the hostgroup for machines that need this specific kernel.
We then built the hosts successfully.
Post-build, the Operatingsystem was set to 'Ubuntu 12.04.4 LTS'. This then caused a re-build of the system to fail, as the wrong kernel was installed.
I suspect the error is around line 47 in app/services/facts_parser.rb, as for our host, the os.description field is blank, because it is filled from the hostgroup. I am unclear on what a good fix for this is, but I will try and dig into more and produce a pull request, unless someone has an easy idea on it.
Another thought of mine is that facts collection should not overwrite fields that are critical to the provisioning process.
Updated by Dominic Cleal over 10 years ago
I think it's likely creating a new OS if the exact major/minor numbers aren't found on the existing OS, this might contain the ".4" too.
Updated by Aaron Stone over 10 years ago
There are at least three problems here, all of which are caused by Foreman reassigning the Operating System out from under us.
Problem 1: I assigned the host an OS, but Foreman invented a new OS entry instead of leaving it alone.
Problem 2: I assigned the host an OS, but Foreman reassigned the host to a different OS with the same name and version, because two entries with matching name and version numbers could be returning in different order from the database at different queries. Instead of leaving it alone.
Problem 3: I assigned the host an OS, and months later did a package upgrade which changed the OS micro version, causing Foreman to reassign the OS instead of leaving it alone.
We have operating System entries like "Ubuntu 12.04 + 3.2.0 kernel" and "Ubuntu 12.04 + 3.13.0 kernel". Based on which OS I assigned to a machine, I have different netboot, templates, and parameters. These are set up as:
Name: Ubuntu
Major: 12
Minor: 04
Description: + 3.2.0 kernel
/ Description: + 3.13.0 kernel
/ Description: with alternate netboot, etc.
Can we disable Foreman from reassigning the OS based on the received facts?
Should we be using some other mechanism to control the host OS installation parameters!?
Updated by Dominic Cleal about 9 years ago
https://groups.google.com/forum/#!topic/foreman-dev/d2OWhUG3J_A has some discussion.
Updated by Dominic Cleal about 9 years ago
- Related to Bug #11937: Yum updating a managed host can invalidate its data in Foreman. added
Updated by Dominic Cleal about 9 years ago
- Has duplicate Feature #12235: OS minor versions should all use the same templates, installation media, and partition tables added
Updated by Dominic Cleal about 9 years ago
- Related to Bug #12076: Unable to create Mulitple OS with same name, major, minor added
Updated by Trey Dockendorf over 8 years ago
- Related to Feature #15078: Disable updates to operating system from Puppet facts added
Updated by The Foreman Bot about 8 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/4077 added
Updated by Anonymous about 8 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset ef9f2f9d14ac0a501c76e23b3d2aca39b267943a.
Updated by Dominic Cleal about 8 years ago
- Assignee set to Trey Dockendorf
- Translation missing: en.field_release set to 209