Categories

  • 13k Topics
    115k Posts
    W

    @Tom-Elliott Thanks fo the quick reply!
    I did rerun the installer today and it seems to be working now, thanks a lot for the quick feedback and fix!

  • Get the latest news on what's happening.
    203 Topics
    844 Posts
    Tom ElliottT

    The eighteenth release candidate for FOG 1.6.0 is available on the rc-1.6.0 branch. It reports version 1.6.0-RC-18.

    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-17

    FOS checks the server’s TLS certificate (#1978, #1980). The boot menu sends FOS the server’s public-key pin as fogpin=. FOS refuses a server whose key does not match. With no pin, FOS checks the chain against its own CA bundle. If that check fails, FOS warns once and continues. New task type: Performance Test (#1982). It is an advanced task. FOS times disk reads, network reads and decompression on the client, names the slowest one, and changes nothing on the disk. The host’s Performance tab, under History Items, lists each result. This adds schema 444. Audit: work that no person did is recorded as (system), not fog (#1984). fog is also the default admin’s username, so a rejected API token or a host that FOS registered looked like the admin’s action. This applies to the Audit Log, to Created By on records saved with no signed-in user, and to quick-registration tasks. Rows written before the update keep fog. Task e-mail through ${user-name} does not change. FOG_KERNEL_RAMDISK_SIZE describes what the value now does (#1986). This adds schema 445. It changes the text only, not the value.

    FOS (kernel and init), from the Latest FOS release

    An RC install or update downloads the Latest FOS release. Latest is now EXP_20261027-181357:

    Kernel 6.18.59, the current 6.18 LTS release. FOS verifies TLS, which is the client half of #1978. The Performance Test task. x64 and x86 boot an initramfs, not an ext2 initrd (FOGProject/fos#75). The file names stay init.xz and init_32.xz, and the boot menu does not change. /tmp is now a real RAM disk with a size limit: FOG_KERNEL_RAMDISK_SIZE sets the size, kept between 64 MB and half of the client’s memory. Warning: a customized init can no longer be loop-mounted. Add your files as an overlay cpio appended to init.xz instead: https://docs.fogproject.org/en/latest/kb/how-tos/customize-the-fos-init/ . A post-init script needs no rebuild at all: https://docs.fogproject.org/en/latest/kb/how-tos/post-init-scripts/ If a client fails to boot with this init, go to FOG Configuration > Initrd Update and install the init from EXP_20261027-155909, the last ext2 init. Then report it on FOGProject/fos#75.

    API documentation: https://docs.fogproject.org/en/latest/1.6/kb/integrations/api

    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 rc from your FOG checkout. A 1.5 server installed from git: update to the current 1.5 stable, then run bin/updatefog.sh --channel rc from 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.

  • View tutorials or talk about FOG in general.
    2k Topics
    19k Posts
    Tom ElliottT

    @Dominique If you’re able to, I’d highly suggest to snapshot the server first, or otherwise ensure you have a path to reinstall php down to 7.2 just incase updating to 8.X breaks your 1.5.10 availability.

    No, you shouldn’t need to re-install fog after updating PHP, but it also wouldn’t hurt anything (but again I highly recommend snapshotting if possible just due to the age of 1.5.10 vs the stable branch code base.)

  • Report bugs, request features, or get the latest progress.
    2k Topics
    21k Posts
    Tom ElliottT

    @delacroix fixparts went missing from FOS during a Buildroot update. The fix (fos#195) landed yesterday, and the first build with it is EXP_20261021-160109. I checked that release: /usr/sbin/fixparts is present in init.xz, init_32.xz, and arm_init.cpio.gz.

    Your debug task boots the init that your FOG server serves, not the one you downloaded. Put the new file in place on the server:

    cd /var/www/html/fog/service/ipxe mv init.xz init.xz.old wget https://github.com/FOGProject/fos/releases/download/EXP_20261021-160109/init.xz sha256sum init.xz

    The hash must match the init.xz.sha256 on the release page (it starts 8e3457ad4268add5). To check the content without a boot:

    xz -dc init.xz > /tmp/init.img debugfs -R "ls -l /usr/sbin" /tmp/init.img | grep fixparts

    Then run the capture again. If fixparts is in that listing and the capture still fails, please post the output of fixparts /dev/sdX (or /dev/nvme0n1) from a debug task.

65

Online

12.8k

Users

17.7k

Topics

157.3k

Posts