08-29-2018 04:30 AM
I had this problem in the past. Turns out a DNA record was set up correctly. Try doing a nslookup on the machine to get ip, then do a nslookup on the IP. Ensure both the machine names displayed are the same
10-09-2018 08:34 AM
I am having similar issue. We are using cloudera on GCP VM using Centos 7.
The problem is even when i have set the hostname to FQDN using hostname from root, looks like gcp reverts back the hostname to shortname causing the dnsTest to fail. Does anyone knows how to resolve this problem? Seems google is running a cron job that sets the hostname to short name.
10-09-2018 08:41 AM
It happened to us when we ported our servers from AWS to GCP using cloud endure. Created GCP VM instance directly and it got fixed.
10-09-2018 08:52 AM
We did not use endure, we are creating new GCP VMs using terraform and installing fresh cloudera manager on top of it. However, the hostname keeps changing to shortname even after setting the hostname to fqdn manually.
10-09-2018 08:59 AM
sad. Basically, hostname gets reset on network restart that happens every few hours in GCP hence the issue. GCP support suggested us to reset it using cron but that completely f**ed up our server communication. Suggest you to get in touch with GCP support since Cloudera or any other entity won't be able to help with this as far as I know
10-09-2018 09:02 AM
Thanks much for the response. We are thinking of creating a cron job that sets it back, but agree it may impact our cluster. We will get in touch with GCP support to understand alternatives. Thank you.
10-09-2018 09:04 AM - edited 10-09-2018 09:04 AM
Setting the cron job will take this particular error away but eventually, you are bound to run into a lot of other issues.
Feel free to try though. Also, let me know your experience after trying that :)