@Wayne-Workman while I realize this is very old, I feel I must add, the legacy clients Config files always defaulted force reboot to off. It is this I imagine is the meaning of lazy mode.

I’m informed that upload/capture task types are not counted in the queue by default due to their minimal bandwidth requirements.

Another thread being solved because this isn’t “directly” a FOG issue, but rather SELinux issue.

I’m sort of ashamed that I haven’t done any of the things I said I’d do in this thread yet 😕 I’ll make it a point to test out the various file types soon.

@Tom-Elliott Added here: https://wiki.fogproject.org/wiki/index.php?title=FOG_Client#Maintain_Control_of_hosts_when_building_new_server

@Wayne-Workman That basically means, HostnameChanger is now fixed.

Fix pushed to fix the green screen.

For those that are wondering, here are my brief instructions for installing ChromiumOS onto the Elitebook.

Arnold The Bat - latest special build (x86 or x64)
http://arnoldthebat.co.uk/wordpress/chromium-os/

Burn to flash drive or hdd per his instructions:

Linux:
Extract with p7zip
burn to drive using:
dd if=ChromeOS.img of=/dev/sdX bs=4M

Windows:
extract using 7zip
burn to drive using https://launchpad.net/win32-image-writer/

Boot

Go into chros shell with:
Ctrl + Alt + F2

Username is chronos
password is password

Install OS:

/usr/sbin/./chromeos-install --dst /dev/sda

@Tom-Elliott I think storage node passwords are stored in the DB as plain-text.

It does not change the password in the DB unless I hit the update button - which happened once.

I was correcting the interface name and did not know the password field was changed, hit “Update” and boom, imaging doesn’t work lol. I figured it out eventually and then narrowed in on what caused it…

I don’t think it was incorrectly set by installer, but rather, it was incorrect (defaulting to eth0) from a long time ago. Probably before I started reading the name of the interface.

@Tom-Elliott said:

For future reference, -d in bash speak means to test if the directory exists, -f would be the proper argument to test if a file is present.

That makes a lot of sense. Prob would explain the error I kept having…

I believe this is fixed as the delete button for all pages was broken for a little bit. It was not directing to the deletemulti element and this would not have deleted on any page. I’m solving this thread but please let me know if there is still an issue. Thanks.

It works, but it is slow.

I’ve change the code that downloads the client, kernels, and inits. I 'm not going to background it any more as this might be the cause of a partial download. When the script exits, it kills the other backgrounded tasks.

@Wayne-Workman Partially solved…

0_1447746331223_upload-04a3ae86-3b52-4d55-9616-b60f93f3740a

@Tom-Elliott I’ll reproduce and then let you know. I don’t think SELinux was on… This particular case is for a first-time installation on a new server build, I thought the -y option would auto update the DB for me, but it didn’t.

I’ve decided to resolve the thread as the limiter IS in fact working. And most people, you’re right, will only be replicating one image or another.

Don’t know if you fixed another issue yet or not but,

During the full registration process while network booting, on svn 4338 cloud 5323,

We had two locations created but only one option showed up for us to choose in the ? listing.