Project

General

Profile

Actions
Copy link

Bug #7568

closed

Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques)

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

Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
System techniques
Target version:
3.1.20
Pull Request:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Small
Priority:
57
Name check:
Fix check:
Regression:

Description

In #7031 we changed the <FQDN> value.
Before 3.1 it was ignored.

In 3.1 it is used as default value for <RUDDER>/<HOSTNAME>, but for old agents it will be the same value as <RUDDER>/<HOSTNAME>.
So we must patch <FQDN> from system techniques for those agents.

Later, this patching can be removed since agents will have the entry.
Later, this value will event become the default.

Related issues 2 (0 open — 2 closed)

Related to Rudder - User story #7571: Change hostname source to prefer FQDN over RUDDER_HOSTNAMERejectedFrançois ARMAND2015-12-08Actions
Related to Rudder - Bug #7031: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodesReleasedJonathan CLARKE2015-12-08Actions
Actions
Copy link
 #1

Updated by Benoît PECCATTE over 8 years ago

  • Status changed from New to In progress
  • Assignee set to Benoît PECCATTE
Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Related to User story #7571: Change hostname source to prefer FQDN over RUDDER_HOSTNAME added
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.1.5 to 3.1.6
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.6 to 3.1.7
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.7 to 3.1.8
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.8 to 3.1.9
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.1.9 to 3.1.10
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.10 to 3.1.11
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ almost 8 years ago

  • Parent task deleted (#7031)
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ almost 8 years ago

  • Related to Bug #7031: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes added
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.1.11 to 3.1.12
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #16

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #17

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #18

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.18 to 3.1.19
Actions
Copy link
 #19

Updated by Benoît PECCATTE about 7 years ago

  • Subject changed from Fix #7031 in system technique to Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques)
Actions
Copy link
 #20

Updated by Alexis Mousset about 7 years ago

  • Status changed from In progress to New
Actions
Copy link
 #21

Updated by Jonathan CLARKE about 7 years ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Getting started - demo | first install | level 1 Techniques
Actions
Copy link
 #22

Updated by Benoît PECCATTE about 7 years ago

  • Priority set to 65
Actions
Copy link
 #23

Updated by Vincent MEMBRÉ about 7 years ago

  • Target version changed from 3.1.19 to 3.1.20
Actions
Copy link
 #24

Updated by Jonathan CLARKE almost 7 years ago

  • Assignee deleted (Benoît PECCATTE)
Actions
Copy link
 #25

Updated by Alexis Mousset almost 7 years ago

  • User visibility changed from Getting started - demo | first install | level 1 Techniques to Operational - other Techniques | Technique editor | Rudder settings
  • Effort required set to Small
  • Priority changed from 65 to 57

This only happens on old agents (2.11, <3.1.5), so setting visibility to operational.

Actions
Copy link
 #26

Updated by Benoît PECCATTE almost 7 years ago

  • Status changed from New to Rejected

This bug has been fixed in recent versions of Rudder.
A solution is to upgrade your agent.
Another solution is to have a properly resolvable hostname.

Actions
Copy link

Also available in: Atom PDF