@Tom-Elliott The error continues to persist even after the update

The conditions are the master node is set to disabled in a storage group. When you attempt to deploy an image the deploy task get created and the above error is thrown and the page never refreshes only times out. If you pick another menu item them that page is painted.

Should the master know ever be disabled in a storage group? (probably not)
Would this ever happen in the wild?? (probably not)
Does it needs to be fixed ?? (only the developers will know that)

@Wayne-Workman I had to get https://github-production-release-asset-2e65be.s3.amazonaws.com unblocked by our service provider to download the client. that was the part causing the failure.

The same will most likely hold true for anybody else in the UK on the London Grid For Learning Network

@Tom-Elliott super g8

@sudburr Would you be willing to send a copy of your database to one of the developers or moderators? If I had a copy of your DB, I can figure out what’s causing the issue.

Works fine!!!
0_1495619633987_captura_multicast_2.png

@Tom-Elliott
Understood, it’s not what I’d prefer but I see the reasoning.
I’ll submit a feature request.

Please, close the ticket 🙂 I can not repeat the situation.
I try several times and now works fine

I’ve updated the code.

Please install the working branch and you should have the ability to use 0 and 7 for sundays.

It will proper send 7 as the “sunday” if 0 was set originally too.

This isn’t a bug. This happens on fresh installs because there is nothing to work from.

While I can remove the message, it’s a way for us to know if this is a fresh or upgrade.

It does not impede installation in anyway. I understand it’s not “pretty”, but it ultimately work.

If you do the add host to a group element, as soon as you press the “process changes” button, and scroll back to the top of the page, I’ll bet you see the “Loader bar” telling you “Group created successfully” or something similar.

The loader is only present for 5 seconds.

The idea of the move to ajax in case you must ask is so you could process many hosts in one sitting area rather than have to recycle the load time every time you click process changes.

Glad to help. I’m going to guess the “error” you were seeing was simply it couldn’t use those files to boot from.

Perfect. I’ll do just that.

Yes, that worked.
Thank you.

@Tom-Elliott
Works perfectly now! Thanks a lot!

Thank you sir for your response, it is working correctly…Just updated and was going through the motions checking functions.

@Tom-Elliott it would appear I was having a rather dumb moment, now you have said that about it listing them I do recall that being the case and how/why it displays a list like that… :-$ guess it freaked me out a little… lol

But when I did add snapins to a group and then went to membership -> host it didn’t have any of the snapins. It is however working now (I did update to rev 96 I realise that has nothing to do with it and also had to reboot for something else)

@alh The mobile flag isn’t displayed on the list/search pages, though it’s certainly something that can be added.

Fixed in working thanks.

@george1421

https://forums.fogproject.org/topic/9888/remove-your-webroot-redirect-to-fog-when-going-to-rc4/9

This post seems to solve the issue.

@Tom-Elliott will you please slow down!! I was just spinning up a new FOG install to prove out the error!! I guess all I have left to do is go get a beer now and relax.