I have two real customer case about this issue.
If other partner have your story , please also update yours, thanks.
Both the two customer their cluster member's original host name are fw1 and fw2.
After upgrade R80.10 , the validation check show the FW1 host name conflict with the TC service object "FW1".
PS: R80 Management with R77.30 Gateways without this validation issue.

So I need to change gateway host name.
But it can not be change directly from here.

So I try to move it out of the Cluster object to reset the Gateway object name.
After "Remove" it, I found the "fw1" Gateway object no longer exist.
I need to create it again.
This my 2017Q3 audit logs.

