Project

General

Profile

Bug #7421

FusionInventory --scan-homedirs should not be on by default

Added by Florian Heigl almost 2 years ago. Updated 8 months ago.

Status:
Released
Priority:
N/A
Category:
Initial promises & sys tech
Target version:
Target version (plugin):
Severity:
User visibility:
Effort required:
Priority:

Description

The system promises have a feature in fusioninventory that searches all user homedirs for virtual machines stored there.
It's used to related those virtual machines to a rudder client's inventory.

This combination:
Virtual Machines installed
Virtual Machines in user's homedirectory

is more of a desktop thing.

Running this on servers with 100s of user homedirectories is a massive IO waster, if it gets into scanning NFS mounts it gets even worse, might take hours or days to complete depending on the size of the server.

Could you please make this a configurable opt-in feature?

($here we're stripping it but it would be enough to be able to just have it configurable)

Associated revisions

Revision 39c91e8d
Added by Benoît PECCATTE 9 months ago

Fixes #7421: FusionInventory --scan-homedirs should not be on by default

History

#1 Updated by François ARMAND almost 2 years ago

  • Assignee set to Benoît PECCATTE

Seems perfectly reasonnable, and the default should be to not scan.

Benoit, could you look to that, please ?

#2 Updated by Vincent MEMBRÉ almost 2 years ago

  • Target version changed from 3.0.12 to 3.0.13

#3 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.0.13 to 3.0.14

#4 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.0.14 to 3.0.15

#5 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.0.15 to 3.0.16

#6 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.0.16 to 3.0.17

#7 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 3.0.17 to 2.11.23

#8 Updated by Vincent MEMBRÉ over 1 year ago

  • Target version changed from 2.11.23 to 302

#9 Updated by Alexis MOUSSET over 1 year ago

  • Target version changed from 302 to 3.1.12

#10 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.12 to 3.1.13

#11 Updated by Vincent MEMBRÉ about 1 year ago

  • Target version changed from 3.1.13 to 3.1.14

#12 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 3.1.14 to 3.1.15

#13 Updated by Vincent MEMBRÉ 12 months ago

  • Target version changed from 3.1.15 to 3.1.16

#14 Updated by Vincent MEMBRÉ 11 months ago

  • Target version changed from 3.1.16 to 3.1.17

#15 Updated by Vincent MEMBRÉ 10 months ago

  • Target version changed from 3.1.17 to 3.1.18

#16 Updated by Benoît PECCATTE 9 months ago

  • Target version changed from 3.1.18 to 4.1.0~beta1

Since this is a behaviour change, let's change it in next release

#17 Updated by Benoît PECCATTE 9 months ago

  • Status changed from New to In progress

#18 Updated by Benoît PECCATTE 9 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Benoît PECCATTE to Nicolas CHARLES
  • Pull Request set to https://github.com/Normation/rudder-techniques/pull/1094

#19 Updated by Benoît PECCATTE 9 months ago

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

#20 Updated by Vincent MEMBRÉ 8 months ago

  • Status changed from Pending release to Released

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

Also available in: Atom PDF