Failed to start tasking type Capture; Could not find any nodes containing this image
-
@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.
-
@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.
-
@Wayne-Workman My image looks pretty much identical to your screen shot. The exception is that my image is assigned to " default."
-
@williams402 Is your storage node set as master? Look in
Storage Management -
@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 the storage node within the storage group (DefaultMember probably) “enabled?”.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
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.
Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG! Get in contact with me (chat bubble in the top right corner) if you want to join in.
Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)
Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG
-
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.
-
@Tom-Elliott Yes the storage node is enabled.
-
@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.
-
@Wayne-Workman Yep I am willing! Thanks!
-
@williams402 I’ve fully released RC-14 now. Please update however you normally would to see the latest.
-
Im having the same probleme. But i dont have any Storage Node.
Is this normal ?
Im on RC 14
-
@Tom-Elliott
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 -
@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.
