Deploying Single Snapins to Group All
- FOG Version: 1.3.4
- OS: Ubuntu 14.04
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
@MarkusK I can only imagine the “SnapinTasks” table is filled with erroneous data.
You could test this theory by: (It will remove any snapin history of course.)
TRUNCATE TABLE `fog`.`snapinTasks`; TRUNCATE TABLE `fog`.`snapinJobs`; DELETE FROM `fog`.`tasks` WHERE `taskTypeID` IN (12, 13); DELETE FROM `fog`.`snapinAssoc` WHERE `saHostID` NOT IN (SELECT `hostID` FROM `fog`.`hosts`) OR `sSnapinID` NOT IN (SELECT `saSnapinID` FROM `fog`.`sID`);
Because of all the “changes” I’m suggesting, I would highly suggest getting a backup of the database before performing these actions. This can be done from FOG Configuration Page->Configuration Save->Export
@Tom-Elliott Image name sounds logical and is not so necessary. I only prefer to see the active snapin tasks and I wonder why they execute but I can’t see them under “Active Snapin Tasks”.
@MarkusK the image name is not important if the tasking is a snapin tasking.
@Tom-Elliott I did some more tests. All snapins deploy to the host, but they are not correctly displayed under “Active Tasks” or incomplete under “Active Snapin Tasks” (The Image name is missing, when submitting a single snapin task to a group".
@MarkusK Why would “image” be visible or not?
Essentially, the tasks link into a snapin job. Those jobs are what are used to determine what’s available for the host to use.
Either it’s working, or it’s not working.
@Tom-Elliott I upgraded to
Running Version 1.4.0
SVN Revision: 6069
but the problem is still there. The second time I submit a single snapin to the same group, there is no Task visible under “Active Snapin Tasks”. Only the first time I submit a single snapin, the Tasks are created.
Looking for the missing tasks, I found out, that there are tasks visible under “Active Tasks”, but the Image field is empty.
@Tom-Elliott Thanks, I’ll give dev-branch a try next week.
@MarkusK Sure. Just make sure you’re on dev-branch.
@Tom-Elliott It’s maybe two weeks ago since. Should I give it another try?
@MarkusK have you updated?
@Tom-Elliott I pulled and updated my installation again. Now I do no longer reproduce the blank page on Active Tasks page.
The first problem I have still exists. I can submit a Single Snapin to a group. The Snapin Tasks are showed on the Active Tasks page. I can submit another Single Snapin to the same group. There are no error messages, but the second Single Snapin does not show up under Active Tasks page. I only see the Tasks for the first submit.
@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.
@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 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 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?
So, I’ve updated to enable the usage of groups to deploy single snapins properly now. Please see:
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.
@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.
@Junkhacker I have no imaging tasks running during the creation of snapin tasks. Scheduled tasks can be sumitted, but never run.