The tenth release candidate for FOG 1.6.0 is available on the rc-1.6.0 branch. It reports version 1.6.0-RC-10.
Test it on a lab or non-production server first. The upgrade from 1.5 to 1.6 is one-way: it changes the database schema, and there is no down-migration.
Changed since RC-9
- iPXE: boot no longer freezes on some UEFI firmware (forum 18271, #1857).
default.ipxeread theSecureBootandSetupModeEFI variables. On some older firmware that read never returns, and the host froze before the menu. The installer no longer writes those two lines. Run the update to rewritedefault.ipxe. Hosts no longer report their Secure Boot state on PXE boot. FOS still reports it when the enrollment task runs. - CSV import reads a file that FOG exported (GH-1851, #1855). "CSV (All)" starts the file with a UTF-8 byte-order mark. The import did not skip it, so it did not find the header row. It imported the header as a host, and the row failed with "No viable macs to use". The import now skips the mark.
Before you upgrade
- Back up your database and
/opt/fog/.fogsettings. - Read the release notes: https://github.com/FOGProject/fogproject/blob/rc-1.6.0/docs/release/1.6.0-release-notes.md
- 1.6 removes Display Manager, Directory Cleaner, User Cleanup, Client Updater, Green FOG and the persistentgroups plugin. Their data is dropped. The site and accesscontrol plugins move into core.
- PHP 7.4 or later is required. Plugins built for 1.5 do not load.
Install or update (as root)
- A 1.6 beta or RC server: run
bin/updatefog.sh --channel rcfrom your FOG checkout. - A 1.5 server installed from git: update to the current 1.5 stable, then run
bin/updatefog.sh --channel rcfrom the checkout. - A new server, or a 1.5 server installed from a tarball:
curl -fsSL https://raw.githubusercontent.com/FOGProject/fogproject/working-1.6/bin/bootstrap.sh | bash -s -- --channel rc
Report problems
Open an issue at https://github.com/FOGProject/fogproject/issues. Include your FOG version, your OS, and the installer log from bin/error_logs/. Report a security problem through "Report a vulnerability" on the same repository, not in a public issue.