User story #7571: Change hostname source to prefer FQDN over RUDDER_HOSTNAME - Rudder - Issue Tracker

Custom queries

8.1 beta
Bugs triage
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

User story #7571

closed

Change hostname source to prefer FQDN over RUDDER_HOSTNAME

Added by Benoît PECCATTE almost 9 years ago. Updated over 8 years ago.

Status:

Rejected

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

4.0.0~rc2

Pull Request:

https://github.com/Normation/ldap-inv...

UX impact:

Suggestion strength:

User visibility:

Effort required:

Name check:

Fix check:

Regression:

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.

Subtasks 1 (0 open — 1 closed)

User story #7578: Fix tests since we change order of hostname

Rejected

François ARMAND

2015-12-08

Actions

Related issues 2 (0 open — 2 closed)

	Related to Rudder - Bug #7568: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques)	Rejected					Actions
	Related to Rudder - User story #8022: Allow users to specify node hostname (FQDN)	Released	Alexis Mousset				Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Benoît PECCATTE almost 9 years ago

Tracker changed from Bug to User story

Actions

Copy link

Updated by Vincent MEMBRÉ almost 9 years ago

Status changed from New to In progress
Assignee set to Vincent MEMBRÉ

Actions

Copy link

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

PR https://github.com/Normation/ldap-inventory/pull/75

Actions

Copy link

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.

Actions

Copy link

Updated by François ARMAND almost 9 years ago

Applied in changeset ldap-inventory|899ef55c3c654550dff4eb3677bfbfb305fbe73b.

Actions

Copy link

Updated by Vincent MEMBRÉ almost 9 years ago

Status changed from Pending release to Discussion

Actions

Copy link

Updated by Vincent MEMBRÉ almost 9 years ago

Reverted by 1b6dbc23b0bb9920f2304fdb4af6aec2ea0ecdbc

Actions

Copy link

Updated by Vincent MEMBRÉ almost 9 years ago

Parent task deleted (~~#7568~~)

Actions

Copy link

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

Actions

Copy link

#10

Updated by Benoît PECCATTE almost 9 years ago

Target version changed from 3.2.0~rc1 to 3.2.0~rc2

Actions

Copy link

#11

Updated by Benoît PECCATTE almost 9 years ago

Target version changed from 3.2.0~rc2 to 3.2.0

Actions

Copy link

#12

Updated by Vincent MEMBRÉ almost 9 years ago

Target version changed from 3.2.0 to 3.2.1

Actions

Copy link

#13

Updated by Vincent MEMBRÉ over 8 years ago

Target version changed from 3.2.1 to 3.2.2

Actions

Copy link

#14

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.

Actions

Copy link

#15