FOG Hangouts

@datnt2509 Which version of FOG do you use? The most current version compiles iPXE for you including all the HTTPS stuff and certificates, so there shouldn’t be any need for manual compiling it.

@benjamind said in Multicast with multi-NIC FOG server:

I have change the interface from ens18 to ens19 in FOG Configuration => FOG Settings => Multicast Settings but when i start a deployement task it still uses the “main” interface as i hace see it in the /opt/fog/log/multicast.log :

You need to restart the service to have it use the new setting: systemctl restart FOGMulticastManager

@astrugatch Quazz is spot on with what he says.

@astrugatch Looks like there would be an edge case if you answered ‘no’ to php/apache reinstall during update where it would just carry on with the ‘packages’ line from .fogsettings and thus cause no problems.

@astrugatch https://github.com/FOGProject/fogproject/commit/29af4df767775e08fc102ea1cf61b4da789b61d5

Fixed on dev as far as I’m aware, but essentially the issue was that moving from Mysql to Mariadb caused the database to not be moved properly and thus it would appear as if the database is gone to the end user.

If you’re already on the dev branch or if you already had Mariadb installed then you’re likely fine.

@sudburr said in FOG 1.5.7 Officially Released:

That also goes for going forward, using for example a 1.4.4 system, how far up the food chain can one go with the kernels for testing?

Pretty much the same answer as I gave you before!

Please be aware that DB-wise going forward/upgrading is supported but going back is NOT!!! Not even a single version. While it should work for some version steps it surely causes issues that are really hard to track down. I suggest, never downgrade unless you have a backup of the old version DB and really know what you do. Snapshot is a save was to Go though.

Things can break from time to time, and given the sheer variety of … variety, it’s good to know for testing purposes if there is a cutoff for how far back one can go for testing before you reach incompatibility.

That also goes for going forward, using for example a 1.4.4 system, how far up the food chain can one go with the kernels for testing?

@sudburr Just so you’re aware - we are still working on the 1.5.x version of FOG. Long term aim is to finish that, merge all the things into the 1.6 branch (Tom does this every now and then with all the fixes we add in 1.5.x) but we’ll most certainly release one or two more 1.5.x versions before we call it “finished”.