Failed to obtain lease on eth0 after ugrading to Fog 1.3.0

[asbenavides]

@Wayne-Workman only one fog setup and I already verified the boot file and everything else

[asbenavides]

@Wayne-Workman and only one Storage Node called DefaultMember as it was created by installation

[Wayne Workman]

@asbenavides Is the DefautMember marked as master? Also, check and see if the image is set to the Default group ? Image Management -> List all images -> click the image -> Storage Group. Is the default group there? Is it marked as primary or not? I’m not asking you to change anything, I’m just gathering info. What is your maximum clients set to? Storage Management -> click DefaultMember -> Maximum clients. Are there other pending image deployments in Task Management?

Also, can you post a picture of the error?

[george1421]

@Wayne-Workman OK to state where we are (still not happy but…)

We’ve got past the pxe booting and are now at the exit mode for uefi

I would like you to unhide the FOG iPXE menu for a few tests. I want to ensure that you can make menu selections and have the target system function correctly. What I’m interested in is the compatibility test, check for both network and storage media. I also want to ensure that you can register a target computer using the ipxe menu. If you can do that then the target and fog communications are working well.

The part I think is failing is the exit mode for these devices to boot from the devices internal media. But lets take one step at a time and test each bit then work on the exit modes (usually what causes the most pain once you get the FOG iPXE menu to display).

OK scratch that, I missed the post with the error about the storage node.

[Sebastian Roth]

@asbenavides said in Failed to obtain lease on eth0 after ugrading to Fog 1.3.0:

"PHP Fatale error: Call to a member function getMasterStorageNode() on null in /var/www/html/fog/lib/reg-task/taskqueue.class.php on line 28

I think it’s best if you double check those storage node settings. Looking at the code I don’t really see why this is going wrong. Best if you can upload some pictures of the settings in the web gui so we can all check and find the issue.

[asbenavides]

@asbenavides

[asbenavides]

@asbenavides said in Failed to obtain lease on eth0 after ugrading to Fog 1.3.0:

@asbenavides

@Sebastian-Roth

[Quazz]

@asbenavides I can already tell that your storage node password is set to password

In other words, it’s almost certainly configured incorrectly.

Please set the password to the one found in /opt/fog/.fogsettings

[asbenavides]

@Quazz okk i changed the password and image uploaded but when it was finalizing it says “Updating Database…FAILED”

[asbenavides]

@Quazz this is what i found under the IMAGES folder in the image was supposed to be named “windows10testing” and it placed the laptop lan mac address as the image name on the folder? how was that possible

[asbenavides]

@Quazz

[Quazz]

@asbenavides This still indicates a FTP password problem. There are likely other places you need to change the password to the one in /opt/fog/.fogsettings

Most likely FOG Configuration -> FOG Settings -> TFTP Server

[Wayne Workman]

If you rerun the fog installer, it will actually correct the password issue. This feature was added because people have difficulty with the passwords.

[asbenavides]

@Quazz I changed the password in the tftp settings and im still getting the error

[asbenavides]

@Wayne-Workman okk I reinstalled fog and the problem now it changed my account password to something that I don’t know?

[Quazz]

@asbenavides The password is the one in /opt/fog/.fogsettings

But you should not be using fog as a linux user to do things on since FOG relies on it quite a bit and you don’t want to get locked out.

I recommend making a new linux user and using that one.

[asbenavides]

@Quazz okk im creating a new account and reinstalling fog