Multiple Deploy Single Snapin tasks - Only last works
In RC5, when you deploy a single snapin to a host, and deploy a second single snapin directly afterwards to the same host (before the first one is processed by the client), Active Snapin Tasks only shows the last deployed snapin as a task.
The following happens step by step:
- Deploy single snapin A to host 1
- Snapin A shows up in both Active Tasks and Active Snapin Tasks
- Deploy snapin B to host 1
- Snapin B shows up alongside snapin A in Active tasks, but replaced Snapin A in Active tasks
- The client will install Snapin B and remove it from Active Snapin Tasks
- Snapin A remains indefinitely queued in Active Tasks, never appears in Active Snapin tasks and never gets installed by the client (client logs no snapins found in c:\fog.log)
This post is deleted!
Great! Compliments for the super quick response and fix. That’s what makes Fog stand out!
RC-6 will have the snapin task cancellation fix.
Like I said earlier:
Snapin deployments work by:
If there’s a Job already scheduled, cancel the originating job and tasks, then create the new tasks and jobs.
So, the “bug” here is the cancellation wasn’t happening properly.
@bluenix right the newest takes over
@Tom-Elliott I understand that there may be a difference between Active Tasks & Active Snapin Tasks, but there are two strange things: 1. The last sent snapin gets executed first, 2. The other snapin never gets executed at all.
The cleanup should be good bit I’ll review it just to be sure.
This is not a bug, it’s intended behaviour. Think of deploying snapins in the same light of multicast tasks. There is the individual tasks per each snapin and a controller that manages the integrity of the whole of the tasking.
Wayne Workman last edited by
Thanks for reporting.