Fog client not renaming computers

[Omar.rodriguez]

@Joe-Schmitt @Raymond-Bell

here is the log file 0_1486064852118_fog.log

[Raymond Bell]

@Joe-Schmitt Since this is Ubuntu image i know this is old but i am wondering if he is needing something like this to change the host name on Ubuntu computer
https://forums.fogproject.org/topic/4510/scripts-customization-of-ubuntu-fog-service-for-ubuntu

[Joe Schmitt]

@Omar-rodriguez could you try hitting Reset Encryption Data on the host in the web portal? Also is there a reason why so many network adapters (virtual or real) are present on this machine?

[Omar.rodriguez]

@Joe-Schmitt @Raymond-Bell just want to clarify my concerns:

1. The hostnames aren’t changing on Ubuntu 16.04 with the client installed on the image.

2. When a new imaging task is created for one of the Ubuntu 16.04 machines it doesn’t auto reboot (yes the setting in fog settings is checked), which means I can’t remotely image machines as I could have to physically be there to reboot the machines.

Sorry if I wasn’t too specific in my OP

[Joe Schmitt]

@Omar-rodriguez correct. That’s why I asked

could you try hitting Reset Encryption Data on the host in the web portal? Also is there a reason why so many network adapters (virtual or real) are present on this machine?

What you’re describing is usually just a symptom of a bad authentication handshake.

[Omar.rodriguez]

@Joe-Schmitt Where can i find this in the fog web portal ? BTW the machines are all CLI non have the ubuntu GUI.

Also the reason why they have so many network adapters is because we have various Juniper virtual devices running with the machine.

[Joe Schmitt]

@Omar-rodriguez it can be found by either selecting a host or a group from the web portal:

[Omar.rodriguez]

@Joe-Schmitt Tried that and nothing happened

We also tried more troubleshooting. This is what we were seeing

---

--------------------------------Authentication--------------------------------

2/2/2017 1:48 PM Client-Info Version: 0.11.8
2/2/2017 1:48 PM Client-Info OS: Linux
2/2/2017 1:48 PM Middleware::Authentication Waiting for authentication timeout to pass
2/2/2017 1:48 PM Middleware::Communication Download: http://10.10.100.252/fog/management/other/ssl/srvpublic.crt
2/2/2017 1:48 PM Data::RSA FOG Server CA cert found
2/2/2017 1:48 PM Middleware::Authentication Cert OK
2/2/2017 1:48 PM Middleware::Authentication ERROR: Could not get security token
2/2/2017 1:48 PM Middleware::Authentication ERROR: Could not find file “/opt/fog-service/token.dat”.
2/2/2017 1:48 PM Middleware::Communication POST URL: http://10.10.100.252/fog/management/index.php?sub=requestClientInfo&authorize&newService
2/2/2017 1:48 PM Middleware::Response Error multiple hosts returned for list of mac addresses

Are the mac addresses the problem? is there a place we can change the mac address in a config?

[Joe Schmitt]

@Omar.rodriguez, alright that’s what I suspected when I saw all of the macs. The problem is your installations share the same virtual mac addresses. You can fix this problem by telling FOG to ignore those macs. To quote @Tom-Elliott from https://forums.fogproject.org/topic/8315/response-error-multiple-hosts-returned-for-list-of-mac-addresses

The fix for this is to add that mac address to the FOG Configuration Page->FOG Settings->FOG Client - Host Register->FOG_QUICKREG_PENDING_MAC_FILTER, you can add the whole mac address or a part of the mac address. Using the “partial” address (usually the first 3 or 4 hex pairs) means it is going to filter anything that matches the partial part. This is comma separated. e.g. (00:01:0F,00:02:03:04,00:05:ab:af:ad:ac).

[Omar.rodriguez]

@Joe-Schmitt said in Fog client not renaming computers:

OG Client

Hey Joe just want to give a huge thank you for helping me out. This solved the issue!

For future reference if anyone has the same issue. This is what we were doing on our end. We are running Ubuntu 16.04 server with KVM. We have multiple virtual network devices which created multiple mac addresses. In return trying to deploy the same image from one machine to others caused a conflict with FOG which made the client not work on the machines. Following what Joe quoted tom on fixed our issue. In my instance using the first 3 hex pairs in FOG_QUICKREG_PENDING_MAC_FILTER solved the issue and the client is working as it was intended to