@maxcarpone said in snapins not deploying from storage nodes: Version 1.5.7.4:

I’ve just found out that the management password of my storage node has been truncated by 1 character.
FYI: @Developers

@brakcounty Then what you should have now is a typical setup for having a business network and an isolated imaging network. FOG will work in this configuration no problem as well as you will be able to update fog in the future without making any changes to the network configuration.

@brakcounty If we look at this as just a pure routing issue I would wonder why on the en02 network you have a default router (route) defined of 10.0.0.10 (eno2 IP address). I don’t see what Linux OS you are using, but I would surely look into your network settings for eno2 and remove any gateway value on that interface. You should only have a gateway defined on eno1 so that eventually the FOG server can reach the internet for updates and installation. Typically an imaging network consists of only one subnet so you don’t define a gateway value for the imaging network.

@Deps I would recommend if your setup is not exactly the same as the OP in this thread that you open a new thread.

We will need more information on what type of computer Mfg and Model, what version of FOG are you using and what FOS Linux kernel are you running.

From your description, it sounds like the target computer is not registering correctly or the network adapter’s MAC address is changing between registration and the next reboot.

You really didn’t supply enough information but looking at the error I can give you a direction to look in.

The error is http://192.168.2.10/bootimgs/18.04/casper/vmlinz… does not exist.

So that means you are using the http protocol which has a base directory of /var/www/html/fog from that directory bootimgs/18.04/casper/vmlinz needs to exist. Just looking at the directory you provided there is no base references but I see Ubuntu directory of 18.04_64 which if you translate that to the file not found path 18.04_64 != 18.04 assuming the base path was /var/www/html/fog/bootimgs

@brakcounty Lets find out a bit more about your setup run these commands and capture the output.

ip addr show
ip route show

Which address is for your imaging network and which address if for the management network. You have 2 default routes showing, not generally a good idea.

@astrugatch It never made it to the repo. It was a skunkworks project I was working on. I just went and grabbed the centos version of cctk https://downloads.dell.com/FOLDER05519675M/1/command-configure-4.2.0-553.el7.x86_64.tar.gz to see if I could rebuild the test environment.

@astrugatch said in Secureboot issues:

Isn’t that what command and configure is for (if you’re a dell shop at least)?

Yes, we use command and configure (CCTK) to set default bios settings. I started looking into building cctk into FOS Linux so those bios settings could be made via a post install script. I think that project fell off the table a while ago.

If you are seeing bzImage being transferred you can remove iPXE out of the problem. The default you should have for uefi is ipxe.efi.

Now you should focus on the FOS Linux engine (bzImage). What version is the FOS Linux kernel? I know I have a Dell 7400 2 in 1 with a Dell usb c dongle (as well as a WD15/WD19 docks) that boot into FOS Linux and pick up a dhcp address.

I find it strange that it finds the network adapter, and sees the link come up but can’t communicate over that link. Lets start with what version of kernel are you using? The next part is to schedule a new capture/deploy task but tick the debug check box before you schedule the task. Then pxe boot the target computer that will but the target computer in debug mode so we can key in some additional commands.

@Peter365 The only comment I can make is watch the permissions on the /images directory now. If you run into upload issues issue this command (note is a bit loose with the security, but its not too big of a risk) chmod -R 777 /images