If it’s an imaging task (or rather an init needed tasking, there should not be any menu’s presented to the user) so I’m just guessing this is if the host is in a snapin tasking you’re seeing the issue?
@wayne-workman and @george1421 this has been added for 1.6. I’m not going to try adding it to 1.5 as it is a bit of work to add the tests and the return information is at best rudimentary in 1.5.
One node crashed this morning. I was rebuilding it. The node was still enabled in fog - and because it wasn’t responding it caused the above error and a chainloading issue on hosts. The node that was not working was not the node that technicians were trying to deploy from.
I’ve updated the javascript that handles this. The information is currently in the “working-RC-2” branch of the git repository as this is where I’ve been pushing the minor bug fixes that have come to me.
I’ve added some cursory code that might/should help prevent the separation of the progress elements.
@Wayne-Workman It does look like they both are, those are just the 2 that I have heard about before. Like I said I haven’t used either of them, so I can’t speak as to their merits or shortcomings.
For now I’m solving this. I realize the issue at hand is likely still there, but this (at this point) is not a problem of FOG or the FOG Client in a “bug” form. This seems much more likely to be a problem simply with disk space. Of course feel free to post info as we find more info out.
