User story #7571
closed
Change hostname source to prefer FQDN over RUDDER_HOSTNAME
Added by Benoît PECCATTE over 8 years ago.
Updated almost 8 years ago.
Category:
Web - Nodes & inventories
Description
In 3.1 #7570 RUDDER_HOSTNAME is preferred over FQDN.
We should prefer FQDN, but since this can change the hostname used by rudder on a given node, we should do it in a major release.
This issue makes it a default value in 3.
- Tracker changed from Bug to User story
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/ldap-inventory/pull/75
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
- Status changed from Pending release to Discussion
- Parent task deleted (
#7568)
- Related to Bug #7568: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques) added
- Target version changed from 3.2.0~rc1 to 3.2.0~rc2
- Target version changed from 3.2.0~rc2 to 3.2.0
- Target version changed from 3.2.0 to 3.2.1
- Target version changed from 3.2.1 to 3.2.2
I would also suggest to enable a "hook"-binary, that if it exists, it is executed to resolve the FQDN of the node being run on, since determining how the node is called from "outside" is not always that easy, as it depends on many things:
- Do we use the same DNS Server as the policy server?
- Do we use the same IP to reach the policy server as the default gateway's IP's FQDN? (issue present on multi-homed servers)
- Does the external DNS also know me by the name I think I have? (SUSE's openstack assigns some bogus hostnames like external.server.fqdn)
Or it should be customizable at least via a local variable, but the binary-approach would actually allow you to use a custom logic to reilable resolve how the node is called, even if it is renamed.
Sorry, misread the topic, opened a separate ticket for that at #8022
- Target version changed from 3.2.2 to 4.0.0~rc2
- Status changed from Discussion to Rejected
Given all the comments and work done in #8022, this one is no more relevant.
I'm closing it, see what is proposed in #8022.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by 
Updated by