For reference, setting master node to a group should reset all nodes to the group to no longer be master and define the chosen item. That said, when paired with the Location Plugin, there’s a hook to “trick” the nodes in a location to believe they are also master nodes to enable multicast to happen, maybe this is what made the GUI appear to have two master nodes in a single group?

@Tom-Elliott

So I figured out where I’m seeing this…

I created a new test group… Added members to the group… Removed members from the group. Everything works there.

When I go into an existing group… (One created in older versions of FOG…) It does not delete the members from the group.

Hope that helps!

@Tom-Elliott

Updated to Working branch and everything looks good! I’ll report back on the other issues I reported earlier. Thank you!! 🙂

@Sebastian-Roth yes sorry

@Tom-Elliott thanks just updated, I have upped the memory limit in General Settings (is that what you mean?) The user tracking is displaying now, will have to look at truncating the image log when I get into the office (on mobile atm)

@Tom-Elliott I love the new theme. I have seen the interface through all of the stages of development, from the 0.29 (grey fog as I called it) days to now. I think the new look is clean, sleek, and professional. Plus there are probably a number of things I can’t see directly that are improved on the backend. Well done!

ok thanks for reply i will upgrade my fog version

I don’t know that I consider this a bug as it doesn’t break functionality. I suppose, by technical senses, it IS a bug.

Either way, fixed in working branch now.

If you must see this, please run:

wget -O /var/www/fog/management/default/fog.css https://raw.githubusercontent.com/FOGProject/fogproject/406c89e5522ae0e2f7398432dd4f3186fb13c982/packages/web/management/css/default/fog.css

< /facepalm >

Looks like I picked the wrong week to quit amphetamines!

@Tom-Elliott you are right! That was the problem. I do not know why i have two instances - i will clear and fix it tomorrow! Thank you Tom!

@Tom-Elliott
I am confused,
I have misunderstood how works the plugin. I thought searching users by lhe LDAP Management section enable to check ldap conf is ok.
I will test in the right way.

Thanks Tom

This appears to be resolved now.
I’m going to guess that someone over at Arch Linux botched a build of some package & didn’t know until a day later & fixed it.

Thank you Tom for the explanation. I will redo the image on a 128gb ssd from now on with my setup. consider this solved 😃

@george1421 Thanks for all your help!

@Tom-Elliott oh sorry…my mistake (as always)
“doing it the right way, wil work”
my sources.list was wrong.

Sorry Tom I forget do it. Yes, If I increase the maximum execution time to 60 seconds, the report runs well

@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