Actions
Bug #7568
closed
Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes (impl for system techniques)
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.
Updated by Benoît PECCATTE about 9 years ago
- Status changed from New to In progress
- Assignee set to Benoît PECCATTE
Updated by Vincent MEMBRÉ about 9 years ago
- Related to User story #7571: Change hostname source to prefer FQDN over RUDDER_HOSTNAME added
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 3.1.5 to 3.1.6
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.1.6 to 3.1.7
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.1.7 to 3.1.8
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 3.1.8 to 3.1.9
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.9 to 3.1.10
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.10 to 3.1.11
Updated by Vincent MEMBRÉ over 8 years ago
- Related to Bug #7031: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes added
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.11 to 3.1.12
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.12 to 3.1.13
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 3.1.13 to 3.1.14
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 3.1.17 to 3.1.18
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.18 to 3.1.19
Updated by Benoît PECCATTE almost 8 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)
Updated by Alexis Mousset almost 8 years ago
- Status changed from In progress to New
Updated by Jonathan CLARKE almost 8 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
Updated by Vincent MEMBRÉ over 7 years ago
- Target version changed from 3.1.19 to 3.1.20
Updated by Alexis Mousset over 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.
Updated by Benoît PECCATTE over 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