To help clarify things.

“Active Tasks” only shows the “jobs” that are to be performed, not every detail of that job as that would take up a lot of room about the “overall” task being completed.

Active Snapin Tasks, is where you can see the individual tasks, the host it’s working from, and their current progress states. Of course they only show up when they’re in pending/progress states. When they’re completed they’re no longer considered active.

This is NOT a report of tasks, but rather an “overview”.

Report pages work differently, in that they should display completed items. Though I’ll admit it’s been a bit since I looked it over.

Good to know. I won’t be able to test right away though. I’m busy doing summer stuff right now. I’ll get back to you as soon as possible.

Thanks to @Tom-Elliott again for coming up with a fix so quickly! I am marking this solved then. But I still think having a testcase suite would be really good as we could make changes to the awk code, run the testcases and just be sure to not have it broken for other known cases. I think we could collect data from the community fairly easy as the information is already there (in d1.partitions that people have lying around on their FOG servers by the dozens)…

Fixed the Reboot/Shutdown/None item. Sorry, it was just a missed code logic. I was always setting shutdown or reboot, forgot about the “none” availability. This is now addressed in working.

@Matthieu-Jacquart You are probably looking for this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_MySQL#Database_Maintenance_Commands

@Tom-Elliott Seems to have worked now. Thanks!

Snapins and Printers don’t have preselectors, because this would be a massive performance issue. We have to call all hosts, make comparisons against all hosts, validate which hosts have all the same information, then use that to present. Because of the “associative” nature of snapins and printers, this is much simpler to handle by just presenting them all and showing the user they can add/remove. We don’t have a means to know which are associated (otherwise we’d be making a list of “here’s the hosts that have these snapins/printers”). For this reason, it’s just a selector to allow adding and removing, it’s on you to know what is associated to the whole of the group or not.

Image association isn’t retained because of a bug, this is now fixed in the working tree.

AD Settings should be retained. Printers (as stated earlier) are not retained. Power Management is not retained for the same type of reason as snapins/printers.

Remember, for plugins they’re kind of their own ball game. Plugins aren’t enabled by default and aren’t installed by default. So I’m aware plugins will have some issues while I work towards updating them to be bootstrap friendly. I’ve already fixed the issues for groups/host location not being available which is now also in the working tree.

Storage Icon should be a little better. Part of this delay is because of using the backend to get the data. The backend pulls in all the files from the nodes (even if they’re not needed). I could tweak the code base, but I think using the api to get the data is ultimately a smarter method as it makes things “common”.

This is fixed with RC-3 thanks for reporting.

@Tom-Elliott

Looks like the reports now work. Thanks.

I do suggest that the user tracking report would be much more useful if it listed all record chronologically and showed the timestamp field. The summary report of who ever login in on a machine or what machine a user ever logged into is less valuable than the detailed report that one could filter at the headers based on any of the fields. This makes the snapin log work, and that would work here as well - imho.

Thanks a bunch… please make this one as Solved.

Jim

@Tom-Elliott said in Storage Group in Dashboard Showing 1 Slot in QUEUE But No Tasks Exist:

mysql fixing

I ran the maintenance script found at the bottom of this link:
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL

Several lines deleted rows. The problem is resolved.

Thanks,

Jim

Fixed in working version 6 1.5.0

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