Categories

  • 13k Topics
    115k Posts
    Tom ElliottT

    @piaFOG26 Are you able to confirm if things are now working for you?

  • Get the latest news on what's happening.
    202 Topics
    843 Posts
    Tom ElliottT

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

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

    REST API: changes that can break a script. Check your API tooling before you update. A cancel names one object. DELETE /{class}/cancel with no id is removed, and an id that does not exist answers 404 (#1960, #1969). FogApi Remove-FogObject -type objectactivetasktype sends the removed request. PUT /{class}/join (bulk edit) needs {class}.edit, not .create. POST /group/join on an existing group also needs group.edit (#1967). A list sends JSON null for a NULL column. It sent "" before (#1965). Errors answer 400, 404, 405 or 409 with a {"error": ...} body. An unrouted path answers 404, not 501 (#1962, #1971). REST API: a create that leaves out a field gets the column DEFAULT (#1948). An image created without isEnabled was disabled, and its next capture failed with “Image is not enabled”. REST API: a bulk edit runs the same checks as a single edit (#1958). Loading a node failure by id works (#1955). The pxemenuoptions list sends regMenu as an integer (#1971). The OpenAPI document reports the real maxRows and matches what the API sends (#1944, #1963). Two unauthenticated URL prefixes that matched no route are removed (#1971). Modules: “Not set” follows the module default (#1974). A change to a module’s default now reaches every host left Not set. A new host has no module rows, so it follows the defaults. This adds schema 443: it writes an explicit Off row where a 1.5-era host had a default module turned off, so no host changes state at the upgrade. Warning: ticking a module’s Default now switches it on for every host left Not set, not only for new hosts. Schema 443 protects only modules whose Default is already on. On a server upgraded from 1.5, many hosts have no row for a module whose Default is off, because 1.5 stored “off” as no row. Ticking Default on that module turns it on for all of those hosts at once. Before you tick it, set the module to Off on each host that must not run it. Groups: mass edit a group’s member hosts from the group page (#1940). Installer: a fresh install on Debian 12 no longer stops at sysv-rc-conf (#1943). Installer: a warning when sshd blocks password login for the FOG service user (#1976). Image captures fail at the move step in that case. The installer does not change sshd_config. A Kea install no longer prints the isc-dhcp-server unit error.

    Thanks to cepadugato for the RC-16 test report (#1945). It covered Debian 12, Debian 13 and Ubuntu 24.04, with BIOS and UEFI clients.

    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
    G

    @Tom-Elliott I figured it was more-so on the internal end of things that we had to take care. But, wanted to make sure. Thank you for your response!

  • 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.

70

Online

12.8k

Users

17.7k

Topics

157.3k

Posts