Bug #6711: Hostname in inventory may sometimes be wrongfully in lowercase - Rudder - Issue Tracker

Custom queries

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

Actions

Copy link

Bug #6711

closed

Hostname in inventory may sometimes be wrongfully in lowercase

Added by Nicolas CHARLES almost 9 years ago. Updated almost 9 years ago.

Status:

Released

Priority:

N/A

Assignee:

François ARMAND

Category:

Web - Nodes & inventories

Target version:

3.1.0~rc1

Pull Request:

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

Severity:

UX impact:

User visibility:

Effort required:

Priority:

Name check:

Fix check:

Regression:

Description

On some systems (especially AIX), the hostname in the inventory is always on lowercase; which is wrong
Command

/opt/rudder/bin/rudder-perl -e "use Sys::Hostname; print Sys::Hostname::hostname();"

returns the proper hostname, while sys.fqhost returns an hostname with invalid case

We should use the perl approch, when available (not on Android then) for the hostname

Subtasks 1 (0 open — 1 closed)

Bug #6744: Modify technique to remove manually added HOSTNAME in inventory

Released

Matthieu CERDA

2015-06-11

Actions

Related issues 4 (0 open — 4 closed)

Related to Rudder - Bug #6782: Broken inventory - missing 'FQDN'	Released	François ARMAND	2015-06-23	Actions
Related to Rudder - Bug #7001: If domain name is not set in resolv.conf, the inventory generated is invalid	Released	Vincent MEMBRÉ	2015-07-21	Actions
Related to Rudder - Bug #7015: Some inventories have empty FQDN attribute, mandatory in 3.1	Released	François ARMAND	2015-07-21	Actions
Related to Rudder - Bug #7031: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodes	Released	Jonathan CLARKE	2015-12-08	Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

another solution could be to use hostname in fusioninventory inventory

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

Assignee set to François ARMAND
Target version changed from 2.11.12 to 3.1.0~rc1

this change is too big to go to 2.11, but it would go in 3.1: it is safer to use reliable hostname from fusion inventory

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

Oh ... the Rudder extension in Fusion inventory contains the hostname (but it is only on linux)

In OPERATINGSYSTEM/FQDN we have the fqdn of the node, which exists on AIX, Windows, and is correctly filled (using http://search.cpan.org/~gbarr/libnet-1.22/Net/Domain.pm )

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

according to fusioninventory team, HARDWARE/NAME should be the right one

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

OPERATINGSYSTEM/FQD should have the correct content

However, i'm puzzled by current parsing:
we parse the inventory, and if we have HARDWARE/NAME, we set the node name to this value
then if we have Rudder expansion, we parse them, and use RUDDER/HOSTNAME

the deprecated HOSTNAME seems to be never used

Actions

Copy link

Updated by Vincent MEMBRÉ almost 9 years ago

Status changed from New to In progress
Assignee changed from François ARMAND to Vincent MEMBRÉ

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

Assignee changed from Vincent MEMBRÉ to François ARMAND

Ha, Vincent gave me some more info on this point:
- OS/NAME is not used as the hostname, but as the node.name (tricky...)
- Main value for hostname is RUDDER/HOSTNAME.
- If RUDDER/HOSTNAME doesn't exist, then we use HOSTNAME

HOSTNAME is always lowercase, while RUDDER/HOSTNAME has the proper case

What we want: something consistent
OPERATINGSYSTEM/FQDN is always consistent (proper case with the proper fqdn)
RUDDER/HOSTNAME has the proper case (but without the domain name always, as it uses hostname --fqd that may work per chance (as the proper attribute is --fqdn))
HOSTNAME is always lowercase, and may, or may not, have the domain name
HARDWARE/NAME has the proper case, but without the domain name

So, we should pick OPERATINGSYSTEM/FQDN if available, if not RUDDER/HOSTNAME, if not HARDWARE/NAME

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

Status changed from In progress to Pending technical review
Pull Request set to https://github.com/Normation/ldap-inventory/pull/66/files

https://github.com/Normation/ldap-inventory/pull/66/files

Actions

Copy link

Updated by Nicolas CHARLES almost 9 years ago

Ok, for sanity, we only pick OPERATINGSYSTEM/FQDN
So that we are ensuring consistency of value, it is easier, less error prone, and this value exists since in along time in fusion

Actions

Copy link

#10