I’ve seen the OP’s issue for several years on ~20 fog servers on various hardware platforms (virtual and bare metal), using both resized and non-resized images. I can confirm that this was still an issue on 1.5.8 but today I upgraded to 1.5.9 and it seems to be resolved. Old images still show the incorrect size, but recapturing them updates the image size on client to the correct value, which is approximately the minimum required hard drive capacity on the client when deploying the image.

@JJ-Fullmer said in Surface Go 2 (microsoft surface usb-c ethernet adapter) won't boot bzImage on fog 1.5.9.2 and Getting database update errors:

I will update my install shortly and re-image one of the machines. Will this also change my kernel? Will I need to remake that change for the surface ethernet adapter?

You will need to re-download the 5.6.18 kernel.

Sorry for my late reply, re: the other thread that I started on this. I don’t manage the hardware-side of the FOG server so i couldn’t get the file specified. I was also furloughed from work for some time, so I’ve missed the earlier updates.

@choppaholic26 said in Image replication failing due to syntax error?:

Will running a new install script do an in-place upgrade without breaking anything?

That’s what we try to achieve. But as you know there can always be special cases. So we cannot promise an upgrade with no issues. Make sure you have a backup copy of your database and the images any you can re-build a FOG server in no time.

Don’t get me wrong, I am not saying upgrades don’t work very well. I just can give you an assurance! In most cases (no manual modifications, mostly standard settings) the upgrade runs through without any hickup whatsoever. And even if you bump into an issue we are here to help you. So don’t worry about it. Take a backup copy and go for it.

@Tom-Elliott Thanks for clarification. So from the description it sounds like this is working as intended. The queue is no handled in order but whichever comes along first grabs an open slot.

@Chad @DJslimD1k @fry_p This is fixed in the latest dev-branch and will be in the next release - soon to come.

@jjacobs @Campig Finally found the time to fix and test. It is fixed in the latest dev-branch. For the commit see here.

@Campig This is fixed in the latest. For the commit see here. Thanks again!

@Sebastian-Roth Makes sense to me.
Solved for me

Mod Note: Solving and closing this thread

@OkeriKai said in "Language french" invalid stockage group:

Un dernière question, quand est-ce que la version 1.5.9RC2 sera t-elle stable ?

I don’t have an answer for that. The more people that test 1.5.9RC2 the more happy the developers are to move it to stable. Just don’t forget to go NOW and change the branch back to master so you don’t forget later and wonder why things are not working good.

@skipdawg02 said in Intel NUC10i3FNK Network Adapter Intel i219-V 10/100/1000 Mbps Ethernet not detected:

Thank you for the feedback. That’s strange because it should have worked with 5.6.18 out of the box. We’ll compare the config files to see what else is different.

@whyzzi said in Environment & Fog Client:

Would scheduling shutdown of the snapin to execute happen on fog or the host?

I’m not sure I understand. You would schedule the snapin to deploy on the FOG server but it would execute the command on the target computer.

Ok we will keep this as a feature request. So just to be clear you want to force a log off after a certain idle time then reboot?

(along those same lines) I know there is an auto log off screen saver. When the screen save is started it logs the user off, then would the normal fog restart work correctly?

Hi,
I’m a new user of FOG and I start to use also this plugin ( I modifying the code like itexido suggested and works fine).

But I have the following problem or maybe a bad configuration.
When restricted user creates a host and associated it with a site and when he tried to list the hosts that host is not listed. I need to log in with the administrator profile to re-add the host to the site and after that the host is listed with restricted user
Thanks

As I just stumbled upon this topic again I might update as well. This is fixed upstream and we already use the version fixed by buildroot in version 2020.02.2.

@jmeyer I am marking this solved as we have not heard back on this. Feel free to update this topic if you are still working on this and need help.

It is not happening anymore. The VM is only 18GB. It takes less than 10 minutes to capture and less than 10 minutes to update FOG. Or visa versa.

The only weird thing I have since noticed is during the install process, when are asked to go to fog/management and hit update database, that page no longer shows up. It just displays the fog login screen. So I just go back to the installer and hit ENTER. It seems to work fine.

@JYost Yeah, truly a bug. Fixed in latest dev-branch. Change will be in the next release.

@abulhol This issue should be fixed in latest dev-branch.

Thanks for your answer.

I suggest to reserve /bin/bash to Linux or Mac. Then when booting on Windows, the client could just ignore it (keeping it in queue) because it’s bash.