R8293 - Old Fog client fails hostname change

[adukes40]

I can’t tell you as much in the technical sense, but last week when I updated to 8255 I was still running the 0.10.6 verison of the client and things were breaking. After updating it to 0.11.2, everything worked like magic. I would suggest updating the client to the the new 0.11.2 version.

[MRCUR]

@adukes40 This is an issue with the old Fog client, not the new one.

[Matthieu Jacquart]

@MRCUR Yes, but why not update all your client to new one ?

[adukes40]

@MRCUR Understood. but it is old client on newer version of FOG. During our last hangout this got brought up. Tom and Joe work closely together on making sure FOG and the client work together. It was suggested to me that I update and when I did it all worked perfectly. I am assuming that something changed between the 0.10.6 client and 0.11.2 client with the coding in FOG since those releases that does not work with the older clients.

Joe would be able to explain it more, but I would think updating everything to the newer one would do the trick.

[Joe Schmitt]

The legacy client still has (or should have) compatibility with trunk.

[MRCUR]

@Joe-Schmitt Thanks for the confirmation Joe. That is what I expected and why I reported this as a bug. We will eventually move everything to the new client but that is not something that’s going to happen in 5 minutes with our number of clients/images/etc. and number of people working on this.

[MRCUR]

Paging @Tom-Elliott

[Tom Elliott]

@MRCUR Paging for what?

[Tom Elliott]

said in R8293 - Old Fog client fails hostname change:

rned an er

Oh and if you update all should be working currently.

[MRCUR]

@Tom-Elliott Doesn’t appear to be working on R8325/SVN5790 - or do I need newer?

[Tom Elliott]

@MRCUR Update please.

[Tom Elliott]

Guessing this is working now?

[MRCUR]

@Tom-Elliott I think so. Waiting for confirmation from a tech.

[MRCUR]

@Tom-Elliott Confirmed resolved.