User story #7571
closed
Change hostname source to prefer FQDN over RUDDER_HOSTNAME
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.
Updated by Benoît PECCATTE almost 9 years ago
- Tracker changed from Bug to User story
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from New to In progress
- Assignee set to Vincent MEMBRÉ
Updated by Vincent MEMBRÉ almost 9 years ago
- 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
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset ldap-inventory|5127c3fe1d4a675c26c9fd1b5f1cf10817ead9a1.
Updated by François ARMAND almost 9 years ago
Applied in changeset ldap-inventory|899ef55c3c654550dff4eb3677bfbfb305fbe73b.
Updated by Vincent MEMBRÉ almost 9 years ago
- Status changed from Pending release to Discussion
Updated by Vincent MEMBRÉ almost 9 years ago
Reverted by 1b6dbc23b0bb9920f2304fdb4af6aec2ea0ecdbc
Updated by Vincent MEMBRÉ almost 9 years ago
- Related to Bug #7568: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques) added
Updated by Benoît PECCATTE almost 9 years ago
- Target version changed from 3.2.0~rc1 to 3.2.0~rc2
Updated by Benoît PECCATTE almost 9 years ago
- Target version changed from 3.2.0~rc2 to 3.2.0
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.2.0 to 3.2.1
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.2.1 to 3.2.2
Updated by Janos Mattyasovszky over 8 years ago
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.
Updated by Janos Mattyasovszky over 8 years ago
Sorry, misread the topic, opened a separate ticket for that at #8022
Updated by Alexis Mousset over 8 years ago
- Target version changed from 3.2.2 to 4.0.0~rc2
Updated by François ARMAND over 8 years ago
- Related to User story #8022: Allow users to specify node hostname (FQDN) added
Updated by François ARMAND over 8 years ago
- Status changed from Discussion to Rejected