@thebaz The number of times someone has upgraded the OS of their FOG server and broken FOG is a lot. So many that it prompted me to write this article about five years ago. The article is still valid. My advice is to not upgrade the OS of your FOG server, unless it’s in a VM and you take a snapshot before hand. If it’s not in a VM, your safest choice is to migrate.
@rlair23 What version of fog are you using? And, what have you tried? Are you getting an error?
@wchaney I assume you’re using the dev-branch? To my knowledge, the last official release doesn’t work with Fedora 36. I do know that dev-branch works with Fedora 36.
@ookami said in Expand Registration Info:
register a machine without a disk installed
Pretty sure you can create hosts from the web UI, all you need is the MAC address.
As to your other questions, I suppose you’re talking about the IPXE registration, and not the web UI. I don’t think RAM is a supported field, or DIMM slot allocation either, nor specific details about RAM.
What your looking for is extra fields in the database. Those are easy enough to add manually, but having them show up in the UI is a lot more work, and involves PHP as well as JS, and I’d be very little help in that area. My PHP skills are basic at best, and FOG’s PHP is fairly advanced. As to the JS, I’ve got zero experience with it.
@trev-lchs MemCheck is not a snapin, it’s a built-in fog feature among others. Snapins are things you create that are executed by the FOG Client.
My guess is these were removed from the boot menu of the server you’ve got now. You might poke around in the IPXE boot menu area and see if you can add them back.
@abulhol said in API doesn't work in 1.5.9 dev. Error in route.class.php:
Do you have automated tests for the API?
I do not. But, if someone created some I would be happy to add them to the daily tests.
@nono I’m not suggesting either of the options you listed, I suggest to migrate to a new box.
@cire3 said in FOG Project call for engagement:
Do you have any ability to know how many fog users are out there?
I don’t know how many users there are, but I do know there’s 776 FOG servers operating on the dev-branch. There’s an unknown number of FOG servers out in the wild running on a version older than October, 2020.
@abulhol Upgrading the OS that FOG runs on has mixed results. Sometimes it works, but usually does not. Generally it’s not advised to upgrade the OS to a new major version due to this. It’s usually advised to migrate your FOG server to a new home that has the new OS. There’s a guide for this, and you should still be able to do this even though your old FOG server is broke. https://wiki.fogproject.org/wiki/index.php?title=Migrate_FOG
@abulhol Thanks goes to the developers, all I do is test the distros.
@wt_101 Fog doesn’t support LVM, keep that in mind. If you have more complicated of a setup than a single disk - single partition - single LVM volume, this probably won’t work unless you use RAW image type.
@coe Ok, so for the ones that don’t get renamed by the client, we need the relevant portion of the fog.log file. This is where the client logs events and errors. Please be sure to copy/paste the whole portion, not just a line.
Are you using the fog client, or are you using the FOS renaming capability only?
@manuel-guerrero question - why are you trying to image AWS instances with fog? Are you aware AWS has built-in image capture as well as built-in snapshots you can utilize?
I wonder how many people want to deploy to systems with multiple disks? I also wonder how hard it would be to give fog information on what disk to read the image from, and what disk to write the image to. Maybe a checkbox for “my source and destination systems have multiple disks”. This would then open some additional menus in the FOG UI where some additional detail could be added like expected disk size, maybe other details.
@manuel-guerrero Did you mount the new disk? Where did you mount it to? Fog puts images into /images by default. You can map that directory to a new disk inside of /etc/fstab usually.
Not all buttons are supposed to be compulsively clicked. 
You should only reset encryption for a host when you’re having problems with it, generally.