@george1421 We’re back to no route on host

Going back a bit - no FQDNs are being used anymore and there is no difference between doing this on the same or different subnet. We tested trying this from a blocked subnet and the curl command came back with a similar message - no route to host.

What protocols/services are used to capture and deploy the image through the FOS USB? I can try testing those individually to see if our network friends are blocking them similar to how TFTP was blocked.

@george1421 I am using the FOS USB Boot Device.

I am able to ping the FOG server on a different subnet using both IP and FQDN.

Currently, my status is that I am able to register hosts, but not able to deploy/capture images. Here’s a pic of a GOOD error when registering a host with passed arguments (Registering works 100%).

Here’s a pic of the BAD error when attempting to deploy/capture an image. I no longer see the message about no route to host. It is now a NULL message.

The same arguments are being passed. What part is causing the first menu option to fail when the second menu option works?

Here’s a pic of my grub.cfg (/boot/grub/grub.cfg)

@george1421 here are the results of showmount -e 127.0.0.1

HTTPS is being used. 149.166.139.13 does point to in-info-fog.soic.iupui.edu.

Our current boot setup is using a FOS USB drive (TFTP issues, we’re working with our overarching network team on that). The target is not currently on the same subnet as the fog server. When testing targets on the 139 subnet, the boot process failed on the step where it verifies internet by running ‘curl -Ikfso /dev/null https://in-info-fog.soic.iupui.edu/fog/index.php --connect-timeout 5’ in init.d/S40Network, so I’m expecting our networking friends have something funky going on with the routing. I will be able to do more tests and update in the next few hours.

I’ve looked at https://forums.fogproject.org/topic/6898/fog-problem (also forgot to change my timezone), but was not able to fix the root problem.

This issue occurs on multiple computer models. I recently got done customizing a boot loader and am booting FOG through GRUB. We can successfully register hosts, but when testing image creating/deployment this popped up.

As a part of the testing process I deleted the default storage node and storage group and created new ones.

The IP address is correct, but for a few other fields we have the FQDN instead of the IP. It doesn’t look like that made a difference here.

Any ideas/tips?