Deploying Single Snapins to Group All
-
Server
- FOG Version: 1.3.4
- OS: Ubuntu 14.04
Description
I have problems deploying several snapins to all hosts.
I deleted all active tasks, active snapin tasks and scheduled task. I created a group called “All” and added all hosts as members.
I select the group “All”, Advanced, Basic Task, Single Snapin and deploy a snapin (.exe) with Schedule Instant (.exe). That works fine.
I select athe group “All”, Advanced, Basic Task, Single Snapin (.exe) and deploy another snapin with Schedule Instant.The error message:
Failed to create tasking to some or all All Failed to start tasking type Single Snapin There is a host in a tasking
A way to avoid this message, is to choose “Schedule Delayed”, choose a date in the future and deploy. The problem is, that this task get stuck in the “Scheduled Tasks” forever and never deploys the snapin.
I also can deploy the same snapin via manage hosts, choose a host, basic tasks, advanced, single snapin. That works. But repeating this for 180 hosts is not so funny.
This process worked in version 1.2.0
-
Anyone with a hint? I truncated snapinTask, snapinJobs, tasks table with no success. I only added one host to the group, with no success. After I try to deploy a second single snapin I always get the error
Failed to create tasking to some or all All Failed to start tasking type Single Snapin There is a host in a tasking
-
@MarkusK The database maintenance commands should clear out any stale jobs from the database that are preventing you from using groups.
https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_MySQL#Database_Maintenance_Commands -
I cleaned the stale jobs, without success. Is it a bug? Can someone reproduce?
-
@MarkusK Did you run all of those commands though?
-
@Wayne-Workman Yes, all of them. Can you reproduce the error?
-
@MarkusK I think Tom did some work on groups and snapins, those changes are in 1.3.5 stable, can you update and see if it’s still an issue?
-
@Wayne-Workman I upgraded to 1.3.5 and have still the same error.
I create a group, add one host into the group and deploy a single snapin to the group. The second time i want to deploy a single snapin to this group, I always get the error:
Failed to create tasking to some or all
All Failed to start tasking type Single Snapin
There is a host in a tasking -
@MarkusK This is expected.
Snapins are “Tasks” in and of themselves. So deploying a snapin, and “redepoying” immediately after there SHOULD be this error. Groups are not hosts and have no nice means to know about hosts in the same manner as an individual host.
-
@Tom-Elliott said in Deploying Single Snapins to Group All:
ns are “Tasks” in and of themselves. So deploying a snapin, and “redepoying” immediately after there SHOULD be this error. Groups are not hosts and have no nice means to know about hosts in the same manner as an individual host.
I was used to deploy different snapins to the “all” group in 1.2.0 like this. How do you deploy, lets say ugly Flash or Java, every month to all hosts without clicking like hell?
-
@MarkusK Why not just make a pack and perform them independently
-
@MarkusK The methods 1.2.0 worked, but were EXTREMELY slow to perform.
There are many changes between 1.2.0 and 1.3.X. I will see if I can maybe make it work, but they’re not working even remotely close to how it was done in the past. (This is intentional.)
-
@MarkusK I recommend you simply wait until there are no active imaging tasks before you create the snapin task, also you may have some luck with using a scheduled task for this
-
@Junkhacker I have no imaging tasks running during the creation of snapin tasks. Scheduled tasks can be sumitted, but never run.
-
@MarkusK Snapins are also considered “taskings”.
So, if you “schedule” single snapin, each of the hosts in the group now suddenly have a “tasking” in the tasking table (even though it’s not an imaging task).
This is the “tasking” he’s referring to.
-
So, I’ve updated to enable the usage of groups to deploy single snapins properly now. Please see:
https://github.com/FOGProject/fogproject/commit/83d189a4de1017eedb8266b6630f10b73bbde4d9
If you must have/see this now, please switch to the github working branch. I’m not considering this a “feature” as it had existed in the past. I’m not considering this a bug because it did require a whole new logic flow to ensure tasking can be done as expeditiously as possible.
Because of the testing I’ve also moved the tasking submission button to display before the list of hosts in the tasking (as I don’t like scrolling to the bottom of the page just to submit my form element here).
Hopefully this fits the bill for what you needed/wanted properly.
-
@Tom-Elliott Thank you very much for effort!
I moved to the working branch and installed it. After the update I was no longer able to login. I reset the password, but this didn’t help. So unfortunatly I couldn’t test your changes.
I really would like to see this in action, because deploying different snapins to groups is one of my main workflows.
Any chance you can help me testing this?
-
@MarkusK please repull and try again. I meant to remove a “testing” element that I found a similar problem but had reset for other reasons. Readded and pushed.
-
@Tom-Elliott Thanks. I moved to 1.4.0-RC-3. I now can submit several Single Snapins to a group. There’s just some strange behaviour. The first time i submit a single snapin to a group with 100 clients, I can see 100 Snapin Task under Task Managment…Active Snapin Tasks. The second time I submit a Single Snapin to 100 clients, there are only 2 Snapin Tasks created. When I repeat the last step, aprox. 20 Snain Tasks are created. I somehow also expect 100 Single Snapin Tasks under Task Managment…Active Snapin Task. When I click Task Management…Active Tasks… I only get a white page.
-
@MarkusK The strangeness of what you’re seeing seems to be odd for sure, but not the end of the world right now I suppose.
Can you provide your apache error logs after going to the Active Tasks page? When pages go white as you’re describing it usually indicates a syntax issue, or there was a memory usage issue. If it is syntax related, chances are it will point us to the issue so I can provide a fast fix for the problem.
