@dforce New inits are build and you can simply re-run the installer to pull the new files. Tom also pushed some changes to dev-branch so you might want to do a git pull as well though it’s not needed. If you do so, don’t wonder about a decreased version number. Seems like we had that advanced a little too high at some point and Tom pulled it back now.
As @Sebastian-Roth has suggested, by default groups in fog are nothing more than a means to apply settings to multiple hosts at once.
So taking your example, if you apply image a in group a and refresh the page, you will see group a maintains image a as it’s set.
If you then go to group b and it contains all the same hosts as in group a, then apply group b image to image b, it will have set image b to all hosts in group a. So if you go back to group a, it will show image b as being set.
The way these fields are displayed, if all hosts in the group have the same image defined, it will display that image as being selected.
Groups in fog were not designed to be persistent.this is why you can associate a host to multiple groups at the same time.
Sorry, I wiped the PC. I have a hard deadline to meet to get the old FOG server replaced.
The good news is that a fresh install, starting from zero on bare metal with a Debian 10.2 net install* and a git clone of FOG worked with no FOG related problems. I have successfully collected an image from a local PC in the IT Admin Lab and deployed it across the routed network to two ‘volunteer’ PCs.
So I apologize again for wasting your time.
All I can suggest is that the installer checks if it is being run as a re-installation and posts a warning, and maybe points to some documentation on how to properly do a reinstall. I recognize I’ve incurred some debt here, so I’ll try and post some helpful information for other people.
I very much appreciate the FOG project. Thank you for providing such a useful tool.
*Debian 10.2 net install grabs a DHCP address, and persuading the OS later to use a static IP was a little more convoluted than I expected. Similarly, the default install does not include sudo, which is easy enough to remedy.
@Tom-Elliott I am willing in a heartbeat. The problem right now may be my “history” of the old trunk builds causing some headaches in the past. I have some convincing to do for my boss, but having solid things that are fixed/improved helps the case. I am also probably going to need to take a medical leave soon and want to have FOG be stable while I’m gone. I will look at the features 1.6 and see if I can’t earn that tester badge again
@brakcounty Using FOG with more than one NIC is not officially supported. While it can be setup this way and mostly works it can still cause trouble as we see.
I probably won’t find the time to set this up myself and test but you are more than welcome to investigate in which case it works or fails. If you need assistence on debugging this feel free to ask here.