Project

General

Profile

Actions
Copy link

Bug #7421

closed

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

Added by Florian Heigl over 8 years ago. Updated over 7 years ago.

Status:
Released
Priority:
N/A
Assignee:
Nicolas CHARLES
Category:
System techniques
Target version:
4.1.0~beta1
Pull Request:
https://github.com/Normation/rudder-t...
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

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)

Actions
Copy link
 #1

Updated by François ARMAND over 8 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 ?

Actions
Copy link
 #2

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.12 to 3.0.13
Actions
Copy link
 #3

Updated by Vincent MEMBRÉ over 8 years ago

  • Target version changed from 3.0.13 to 3.0.14
Actions
Copy link
 #4

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.0.14 to 3.0.15
Actions
Copy link
 #5

Updated by Vincent MEMBRÉ about 8 years ago

  • Target version changed from 3.0.15 to 3.0.16
Actions
Copy link
 #6

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.0.16 to 3.0.17
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 3.0.17 to 2.11.23
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ almost 8 years ago

  • Target version changed from 2.11.23 to 302
Actions
Copy link
 #9

Updated by Alexis Mousset almost 8 years ago

  • Target version changed from 302 to 3.1.12
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.12 to 3.1.13
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.13 to 3.1.14
Actions
Copy link
 #12

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.14 to 3.1.15
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.15 to 3.1.16
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.16 to 3.1.17
Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 7 years ago

  • Target version changed from 3.1.17 to 3.1.18
Actions
Copy link
 #16

Updated by Benoît PECCATTE over 7 years 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

Actions
Copy link
 #17

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from New to In progress
Actions
Copy link
 #18

Updated by Benoît PECCATTE over 7 years 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
Actions
Copy link
 #19

Updated by Benoît PECCATTE over 7 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions
Copy link
 #20

Updated by Vincent MEMBRÉ over 7 years ago

  • Status changed from Pending release to Released

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

Actions
Copy link

Also available in: Atom PDF