OS facts should not overwrite the OS selected to provision with
|Assigned To:||Trey Dockendorf|
|Found in release:||Pull request:||https://github.com/theforeman/foreman/pull/4077|
|Velocity based estimate||-|
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.
#2 Updated by Aaron Stone almost 3 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:
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!?
#3 Updated by Dominic Cleal over 1 year ago
https://groups.google.com/forum/#!topic/foreman-dev/d2OWhUG3J_A has some discussion.