Project

General

Profile

Actions

Bug #7015

closed

Bug #7001: If domain name is not set in resolv.conf, the inventory generated is invalid

Some inventories have empty FQDN attribute, mandatory in 3.1

Added by Nicolas CHARLES almost 6 years ago. Updated over 5 years ago.

Status:
Released
Priority:
N/A
Category:
Web - Nodes & inventories
Target version:
Severity:
User visibility:
Effort required:
Priority:

Description

We introduced a change in 3.1 that made the FQDN attribute in inventory mandatory. The reason for that was that the attribute we were relying upon in 3.0 and before (HOSTNAME ?) was sometime badly filled, and the value was not the real fqdn but only the hostname, which proved to lead to errors afterward.

However, in some cases the FQDN attribute may be empty due to bad behaviour of the perl command used by fusion inventory to find it.

So we have two cases to manage:

- correct the bug at fusion inventory level so that on the long run, we can effectivelly rely only on FQDN (maanged in parent ticket #7001)
- find a way to be able to have a Rudder 3.1 server with nodes on Rudder < 3.1 - so actually, use something else than FQDN when that attribute is empty, most likelly what we were using until 3.1 (even if it is sometime filled with a bad value, that will greatly reduce the total pourcentage of error compared to pre-3.1 versions) => this ticket.


Related issues

Related to Rudder - Bug #6711: Hostname in inventory may sometimes be wrongfully in lowercaseReleasedFrançois ARMAND2015-06-11Actions
Related to Rudder - Bug #6782: Broken inventory - missing 'FQDN'ReleasedFrançois ARMAND2015-06-23Actions
Related to Rudder - Bug #7031: Inventory <FQDN> content differs from hostname --fqdn and may lead to unauthorised nodesReleasedJonathan CLARKE2015-12-08Actions
Actions #1

Updated by Nicolas CHARLES almost 6 years ago

  • Related to Bug #6711: Hostname in inventory may sometimes be wrongfully in lowercase added
Actions #2

Updated by Nicolas CHARLES almost 6 years ago

  • Related to Bug #6782: Broken inventory - missing 'FQDN' added
Actions #3

Updated by François ARMAND almost 6 years ago

  • Subject changed from Accept inventories with empty FQDN to Some inventories have empty FQDN attribute, mandatory in 3.1
  • Description updated (diff)
Actions #4

Updated by François ARMAND almost 6 years ago

  • Description updated (diff)
Actions #5

Updated by Nicolas CHARLES over 5 years ago

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

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
Actions #7

Updated by Vincent MEMBRÉ over 5 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/69
Actions #8

Updated by Vincent MEMBRÉ over 5 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #10

Updated by François ARMAND over 5 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.1 which was released today.

Actions

Also available in: Atom PDF