Actions
Bug #21356
closedInventory hostname differ between Windows and Linux
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
First impressions of Rudder
Effort required:
Priority:
158
Name check:
To do
Fix check:
To do
Regression:
Description
Inventory data pulled by Rudder differs between Windows and Linux Hosts. When a Linux we show the full qualified domain name whereas when a Windows we only show the netbios name/hostname
.
Files
Updated by Nicolas CHARLES over 2 years ago
Agent looks for FQDN using the following methods
(Get-WmiObject -class Win32_ComputerSystem).DNSHostName
fallback to
my $getComputerName = Win32::API->new( "kernel32", "GetComputerNameExW", ["I", "P", "P"], "N" );
and fallback to
$ENV(COMPUTERNAME)
but these methods don't seem to return the FQDN if it's set locally, not via the domain controller
it seems* a more reliable approach is to use
[System.Net.Dns]::GetHostByName($env:computerName).HostName
Updated by Alexis Mousset over 2 years ago
- Category set to Agent
- Priority changed from 62 to 124
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 7.2.0~beta1 to 7.2.0~rc1
Updated by Alexis Mousset over 2 years ago
- User visibility changed from First impressions of Rudder to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 172 to 142
Updated by Alexis Mousset over 2 years ago
- User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to First impressions of Rudder
- Priority changed from 142 to 172
Updated by Alexis Mousset over 2 years ago
- User visibility changed from First impressions of Rudder to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 172 to 142
Updated by Alexis Mousset over 2 years ago
- User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to First impressions of Rudder
- Priority changed from 142 to 172
Updated by Alexis Mousset over 2 years ago
- User visibility changed from First impressions of Rudder to Getting started - demo | first install | Technique editor and level 1 Techniques
- Priority changed from 172 to 3382
Updated by Alexis Mousset over 2 years ago
- User visibility changed from Getting started - demo | first install | Technique editor and level 1 Techniques to First impressions of Rudder
- Priority changed from 3382 to 204
Updated by Alexis Mousset over 2 years ago
- Severity changed from Critical - prevents main use of Rudder | no workaround | data loss | security to Minor - inconvenience | misleading | easy workaround
- Priority changed from 204 to 161
Updated by Nicolas CHARLES over 2 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by Nicolas CHARLES over 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to Félix DALLIDET
- Pull Request set to https://github.com/Normation/rudder-packages/pull/2643
Updated by Nicolas CHARLES over 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder-packages|52a1c4257a1ef704ffa0c2d7f3ec3553f0ccd62b.
Updated by Nicolas CHARLES over 2 years ago
- Subtask #21579 added
- Priority changed from 161 to 160
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
- Priority changed from 160 to 158
This bug has been fixed in Rudder 7.2.0~rc1 which was released today.
Updated by François ARMAND about 2 years ago
- Related to User story #8022: Allow users to specify node hostname (FQDN) added
Actions