Failed to start tasking type Capture; Could not find any nodes containing this image
- FOG Version: 1.3.0-RC-13
- OS: Ubuntu 14.04
Client is a Dell Optiplex 790 running Windows 10 Education Edition
@fpsacha After upgrading to RC-14; once I defined the master node (the fog server itself) and made sure all passwords were the same, the process has run seamlessly.
I’m having the same problem, without a storage node.
I do have a default group, and have made it primary.
I’m still not able to capture:
***Failed to create tasking to some or all
HS-01-04 Failed to start tasking type Capture
Could not find any nodes containing this image***
Ubunto Fog Server
Running Version 1.3.0-RC-14
SVN Revision: 5974
Windows 10 clients
Im having the same probleme. But i dont have any Storage Node.
Is this normal ?
Im on RC 14
@williams402 I’ve fully released RC-14 now. Please update however you normally would to see the latest.
@Wayne-Workman Yep I am willing! Thanks!
@williams402 would you want to try out the un-finished RC-14 to see if Tom’s changes work for you? If so, message me and I’ll give you instructions.
@Tom-Elliott Yes the storage node is enabled.
Add-on I’ve also changed the image to always have at least one group associated whether it’s got one or not in the database. As images can belong to multiple storage groups, I’m simply going to use the first storage group in id order.
Through a bit of searching I may have found the issue. I did find am issue in the case an image has no groups assigned logically. This apparently was not the direct fix for your situation but it worked great for mine. That said the issue was with how the items where being loaded.i had a typo … The function that loads this should’ve been loadStoragegroups, but it was loadStorageGroups. This has been corrected for in RC 14. The issue also existed with snapins which was also fixed. I know snapins have no bearing on imaging but I could see it causing potential issues down the road.
@williams402 is the storage node within the storage group (DefaultMember probably) “enabled?”.
@Wayne-Workman I created a node for the server itself and designated it the master node. I deleted the old image and created a new one with the storage set to default. Same result.
@williams402 Is your storage node set as master? Look in
@Wayne-Workman My image looks pretty much identical to your screen shot. The exception is that my image is assigned to " default."
@williams402 Tom is talking about this area here, he wants you to make sure that your default storage group is actually assigned to the image you made.
@williams402 Storage Groups are different from Host groups.
There should be a default group created. Normally this storage group name is called Default. If you only have one storage node yes it should be the “master” system.
@Tom-Elliott Tom, sorry I am a new user and am a bit confused about assigning storage nodes. If I am using a single server as the default storage node, do I need to create a storage node or designate my single server as the master node? Additionally, is it necessary to create a group in order to image devices?
@Wayne-Workman Thanks Wayne. This is a new installation without storage nodes and using the default storage group. I am not using the location plug-in .
Sever - Dell Precision T3500 running Ubuntu 14.04 updated as of 10/12/16
Brand new Fog installation updated to trunk as of 10/11/16
Client - Dell Optiplex 790 running client updated 10/11/16
Created and image call Optiplex790SFF
Completed Full Host Registration with the client via PXE and associated the host with the image
Check the the Host to insure that it is associated with the correct image and then create a basic task "upload"
Receive error message
Confirmed the issue, but it’s not something I can readily fix. Please check the image storage group settings. Make sure it’s in a storage group that has assigned storage nodes.
We need more information. How many storage nodes do you have? How many storage groups? Are you using the location plugin? Is this a pre-existing FOG setup or did you just build it?
Can you provide exact steps for us to replicate the issue in our test environments?