Support Questions

Find answers, ask questions, and share your expertise
Announcements
Celebrating as our community reaches 100,000 members! Thank you!

CDH Express 6.3.1 - Suddenly, hostname changed in CM and Stale Configurations waiting to be applied

avatar
Expert Contributor

Hello, a customer has a CDH Express 6.3.1 setup and:

- It appears that suddenly one (and just one!) of the hosts listed in Hosts --> All Hosts is now showing as having a complete FQDN. It never used to have it (I have screenshots of previous configurations where ALL hosts in the list are shown with just the hostname and no domain)

- Also, there are Stale Configurations waiting to be applied. If I click on them, they are related to a number of Client Configuration files waiting to be deployed, and sure enough ALL the lines in ALL the files are showing a single difference for that particular host!

Now, I don't know what happened here. Nobody is reporting a CM configuration change made by them.

I don't have History/Rollback capabilities on this cluster, as it's an Express Edition. Also, I have no Audits as well to check what (if any?) parameters have been recently changed

I just know that Sysadmins recently performed a change in FQDN names on those hosts at OS level, because a monitoring tool (Zabbix) required it. But according to them nothing has been changed at CM Gui level

My questions:

- How can I manually check what (if any?) parameters have been recently changed in CM Gui? If I'd be able to identify a change/changes where the FQDN has been put in for that host, I could manually overwrite it

- Or maybe the problem could be that CM "detected" a change at OS level (that config made by the sysadmins) and is now proposing a configuration change automatically? I really doubt it, but... Is it even a possibility?

Thank you for any advice/help/support. Unfortunately I'm not directly managing that cluster so any requests for screenshots/checks on the system would receive slow replies... I have to ask the Customer. Knowing that, I eventually encourage to simply point out what configurations in CM can lead to change in single host FQDN changes being distributed in the cluster as client configurations

1 ACCEPTED SOLUTION

avatar
Super Collaborator

hi @FrozenWave if the OS team has changed the FQDN then the agent will capture that change and display the same in CM UI. The agent does # hostname internally to get the FQDN.

 

So this is coming from LINUX's side not from CM's side.

View solution in original post

3 REPLIES 3

avatar
Super Collaborator

hi @FrozenWave if the OS team has changed the FQDN then the agent will capture that change and display the same in CM UI. The agent does # hostname internally to get the FQDN.

 

So this is coming from LINUX's side not from CM's side.

avatar
Expert Contributor

Thank you so much, I'm going to dig more in deep in this direction and update you on the findings!

avatar
Expert Contributor

Thank you again @Rajat_710 . I Asked the Customer to revert the changes the OS Team performed at OS level. At this point, the Stale Configurations were still showing as pending but following a reboot of the "spurious" machine they cleared up. The situation is back to normal. I'm grateful for your valuable insight!