@Matthieu-Jacquart Told ya.

Confirmed working. the CA ssl folders can now be separated from the snap-ins folder

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

@Sebastian-Roth I’m marking it as solved. I cannot replicate.

I set multiple systems up for ONLY All Snapin Tasks.

@Tom-Elliott Yes the settings apply through the group to the hosts in the group.

Found, confirmed, and fixed plus a little.

Snapin associations weren’t being deleted for whatever reason, so I’ve added code to ensure it will do so now.

To fix the systems that currently believe it’s already broken, we do the same thing.

I check the associations, check the valid ID’s, and delete associations that are no longer valid when compared to the two primary tables.

God’s ways are inscrutable 😳

With the new kernel works fine and with the old one no.

Close this ticket, please!!

Yeah!! Works fine

@Tom-Elliott Thanks! Works as expected. And I see the confusion regarding this bug. I didn’t report it very clearly, and you took it mean the the result of the “fog” script within the debug session vs the actual start of the task. I’ll take care to report more completely in the future. Thanks again for all your efforts here!

@Sebastian-Roth I deleted my fog repo and then pulled it down fresh. The THERE! disappeared… 😕

Guess I messed with some code previously and forgot about it. idk, I mess with a lot of stuff lol.

Confirmed found and fixed.

I want to add a caveat to this. I really don’t like relying on OS type as a defining factor. That said, 1.3.0 still relies on OS type to determine if it’s a valid resizable OS (Windows XP,Vista,7,8,8.1,10) and (Linux, Chromium OS). It also relies on the os type to determine the “fixed_size_partitions”. Of course the fixed_size_partitions file can be edited after the upload, but I am still under the impression we should really use it from the GUI. I will work on it, but for now I’m glad this is working.

@Tom-Elliott Also confirmed, it is working now. The sort is still by Captial and the lowercase alphabetic but that’s a minor issue

@mrayzies THat’s exactly what it is. If you update a host’s primary mac, the update is the primary, and the original primary becomes an additional mac.

Sorry I’ve been unresponsive – I’ve been quite busy with tasks at work and probably wont’ update anytime soon. If you think it’s fixed, I’d say it’s fine to close this ticket ----- if/when I upgrade, I can re-open/comment if I still find it to be an issue.

Problem solved, the /var folder was full. Now I can update the version.

I just had this issue as well - and it turned out to be my fault.

In the setup it asks for server and web info.

I put the IP into both fields.

I tried just putting the IP into the top server field and leaving the bottom web field alone.

When I did that, it worked.

@Sebastian-Roth @Tom-Elliott
After an update to the current subverion it’s working again. Thanks.

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

Please let me know after updating…again. I say again because I found I had one thing being encoded where it shouldn’t have been which would cause the failure because it’s passing the password that will NOT be decoded. When it’s performed on command line, however, it needs to be encoded.