FOG 1.3.4 RC 1 Released

[Tom Elliott]

https://news.fogproject.org/fog-1-3-4-rc-1/

[Wayne Workman]

What does this mean?

Fix Host MAC table to only have one mac address (not one per host).

[Tom Elliott]

@Wayne-Workman It means exactly what it states.

1.3.3 and prior allowed One MAC Per host, but the mac itself could show up on Multiple hosts.

This is now corrected for and you will only ever have One MAC Address in the table.

[Tom Elliott]

I guess I don’t know how to clarify.

A MAC Address was allowed once per host. The host could have as many mac’s associated to it as wanted.

For example, host ID 4 could have:

00:01:02:03:04:05,
00:22:22:33:33:44,
00:02:33:33:44:55

And hostID 5 could have the exact same mac’s associated to it.

While this was “legal” to the database and even to the display in the GUI, when it came time to manage a host with matching Mac’s you’d see the “Error multiple hosts returned for mac address” kind of things.

Now, a mac address can only exist once (AND only on one host).

[sudburr]

@Tom-Elliott So what happens if you re-use that external NIC on another laptop when it comes to FOG naming it?

[Tom Elliott]

@sudburr I don’t follow.

[Wayne Workman]

@Tom-Elliott He’s talking about the same thing I was about to ask.

For USB ethernet dongles that are used with many devices, and what of MAC addresses for virtual machines?

[Tom Elliott]

@Wayne-Workman I still don’t follow.

If the nic is the item used to image multiple machines, as long as that mac IS the registered mac, the name shouldn’t change. Other hosts won’t be trying to steal it from one another.

Virtual Machines have duplicate mac’s, yep. If it’s registering as a pending mac, it’s going to be the last host to try to use it. Otherwise you would end up with (Multiple hosts found for this mac) and fail to perform whatever it was going to perform.

In the case of the USB NIC jumping around, I still don’t understand why it would be “jumping” itself.

[Tom Elliott]

I do, however, understand that you’re saying the NIC is being used on multiple machines. You still (even without this change) would not be able to register the nic to multiple machines at the same time. Registration usually adds the MAC in use for registering as the primary mac. The moment you register the first host, any other host using that same nic will not have a “registration” element for the boot menu (because that nic is now registered).

[neodawg]

Just curious what will happen to the existing computers that would happen to have duplicate MACs between hosts? Will it wipe out any dups after the first host that uses it? Or does it leave it be until its host item is manipulated in some way (changed).

[Tom Elliott]

@neodawg When the update occurs it will wipe out any duplicates.

[Tom Elliott]

I still feel like I have to clarify more cause this really isn’t making sense to me. If it’s not making sense to me, how can it make sense to anybody else?

Let’s say you have a USB NIC with primar MAC Address 00:01:02:03:04:05 that’s registered with Name USB_NIC_1

Let’s say you have another device who’s primary MAC Address is 00:22:33:44:55:11 with Name SOME_HOST_1.

Now let’s say you put the USB NIC on SOME_HOST_1.

It would not work. You would get an error stating “Multiple Hosts”. This would be the expected action. Does this make any more sense?

[sudburr]

The circle of logic my head is spinning around is what happens when you have x number of mobile devices that can only connect by using the USBNIC one at a time.

I guess you would be forced to change the host definition before starting each time to avoid auto-naming each subsequent device with the same name.

But then thinking out loud … I’m going to guess that the best practice would then be that the USBNIC must be removed from MOBILEDEVICE_1 before it boots for the first time, so that if there is a pre-installed fog client, it doesn’t confuse the database.

[Tom Elliott]

@sudburr You can set the mac address to “client ignore”.

[Wayne Workman]

I’ve been looking through the commit history between 1.3.3 and 1.3.4 RC1 and I can’t find a commit with a message that has “mac” in it. Exactly what commit does it?

[Tom Elliott]

@Wayne-Workman What do you mean?

The ignore client and ignore image have been in for a VERY long time. They are those checkboxes next to the MAC Addresses.

[Wayne Workman]

@Tom-Elliott I’m trying to find the commit where you did this:

Fix Host MAC table to only have one mac address (not one per host).

[Tom Elliott]

https://github.com/FOGProject/fogproject/commit/3fe54ced5c8beede71434ffc5227b2c1ee97e190

[jjacobs]

Hi Tom,

First I had version 1.3.3 installed and had the error:

26/01/2017 12:25 Middleware::Response Error multiple hosts returned for list of mac addresses

After the update to
Thu Jan 26, 2017 13:22 pm
Running Version 22
SVN Revision: 6063

I still had the following issue:

26/01/2017 14:05 Middleware::Communication URL: http://CA-FOG/fog/management/index.php?sub=requestClientInfo&mac=34:E6:D7:1F:47:3E|48:51:B7:5D:83:42|48:51:B7:5D:83:43|00:09:0F:FE:00:01|48:51:B7:5D:83:46||00:00:00:00:00:00:00:E0|80:93:87:50:50:47&newService&json
26/01/2017 14:05 Middleware::Communication ERROR: Could not contact FOG server
26/01/2017 14:05 Middleware::Communication ERROR: De externe server heeft een fout geretourneerd: (500) Interne serverfout.
26/01/2017 14:05 Middleware::Response Success

When I disabled the Mobile Broadband card (80:93:87:50:50:47) the client (Latitude E7440) stopped giving the error and renamed and joined the computer.

Kind regards,
Johan

[Tom Elliott]

@jjacobs et al,

When you see Server 500 fault, please try to catch the apache error logs. This will tell me more definitively where a problem is. I don’t have systems with mac’s that “could” appear on multiple systems or trying to register a strange mac address, so it’s very difficult for me to help fix any problems. I simply can’t replicate them, so I think all is good to go.

Almost always an error 500 is some sort of syntax error which will show up in your apache error logs.