Failed to obtain lease on eth0 after ugrading to Fog 1.3.0
-
Hello,
im having trouble obtaining an address lease when im uploading the image. I fresh installed the Ubuntu and installed Fog 1.3.0it was working before with the old version of Fog 1.2.0 so im guessing its not my network.
Some advice will be helpful thanks in advance
-
This issue could be in many spots. So we know exactly where, can you post a photo of the issue please? We would need this to help better. Otherwise we would just be guessing.
-
-
@asbenavides Get a mini-switch that is a un-managed dumb switch - place it between the computer and the building. 2 patch cables, 1 from the computer to the mini-switch, 1 from the mini-switch to the building. Try to image. If it works, this means PortFast is turned off for the port you were previously trying to image from.
Also, what kernel does your fog server say it has? Look in the web interface -> FOG Configuration.
-
@Wayne-Workman it says it has kernel 4.7.0 before the one I mentioned it was the 4.7.1 so basically i downgraded to 4.7.0
-
@asbenavides Why did you downgrade? Please try 4.7.1 without the mini-switch.
-
@Wayne-Workman it was giving me the same error i already have the network setup like you advice me
-
@asbenavides How is the network setup? Are you using a mini-switch?
-
@Wayne-Workman my setup is as follow main mdf, mini-switch, then PC
-
@asbenavides Can you try Kernel - 4.3.0 TomElliott - (x86_64) please? Use the kernel update feature. Details on using it are here:
https://wiki.fogproject.org/wiki/index.php?title=Kernel_UpdateIf that doesn’t work, try 4.1 next.
-
@Wayne-Workman no luck with 4.3.0 or 4.1
-
@asbenavides According to this thread:
https://forums.fogproject.org/topic/5886/what-was-default-kernel-in-fog-1-2-0/2
the default kernel for 1.2.0 was 3.15.6. Can you try that? If that doesn’t work, I’ll have to defer to either George, Sebastian, or Tom. -
@Wayne-Workman im going to reformat and reinstall 1.2.0 all over again maybe something got corrupted. Ill try your recommendations once its up and running
-
@asbenavides As a side note, if you are intending to re-install 1.3.0 RC, you don’t need to start with 1.2.0. You can just go straight to 1.3
-
This issue reminds me of a spanning tree issue where the target computer gets an IP address for iPXE but then in the FOS engine it can’t pick up an IP address. This is because spanning tree take 27 seconds to start forwarding data, since the FOS engine is so fast it has already given up by the time the network switch starts forwarding data. Wayne’s recommendation to use a mini (dumb) switch will typically improve your chances of getting an IP address since the building switch port never winks (momentarily turns off and back on) net network link as the FOS kernel takes over the management of the nic adapter. Most enterprise switches have a fast start mode for spanning tree called (portfast, fast-stp, rstp, and a few other names) that is typically turned on for access switch ports.
The other possibility here is that the network adapter is not supported by the FOS engine, in this case the nic will never initialize. I quickly looked through the thread but I didn’t see any mention of the target computer you are tying to boot. What device is this? Is it a physical (on-board) nic or a usb network adapter?
-
@george1421 its a Dell Optiplex 745 small form factor with integrated nic.
-
@asbenavides
If it might be a NIC issue, then I would try using a USB Nic, you might still be able to PXE boot from it and rule that part out. -
@Wayne-Workman I’ve already reinstalled and reformat computer and im getting the same issues…is there any special configs that need to be done to the switch. It worked alright with 1.2.0 but after upgrading to 1.3.0 its doing the same issue…is there any setting in the Fog that can be moved for it to keep the ip address request longer? It just takes a little bit longer
-
@asbenavides On a single port where you have the device connected. Can you ensure that spanning tree is turned off? I don’t usually recommend this because if forgotten can turn into a nightmare if someone creates a loopback with it. But we need to identify if this is a spanning tree issue.
That o745 has a very common nic so that should not be a problem. When FOG 1.3.0 is installed you also get the latest kernels and inits for the FOS engine (the software that captures and deploys images to the target computer). The FOS engine is failing to detect an IP address.
First see if you can disable spanning tree protocol on that specific switch port. Also ensure that any green ethernet functions (802.1az) are disabled on that switch port too. Then pxe boot the fos engine again.
If that doesn’t work manually register the host in the FOG console, then schedule a debug capture. Don’t worry we are not going to upload anything. What this will do is drop you to a command prompt on the target computer. From there we can run some debugging commands to try to understand why this system is going sideways.
-
@george1421 yeah all the ports here at the school district have the spanning tree enabled…that is going to be the issue its not giving the enough time to receive an ip address. Is there a way to tell fog to wait little bit more longer
