Project

General

Profile

Bug #4197

FusionInventory: Doesn't display (most) disk sizes

Added by Olivier Mauras over 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

Apparently fusioninventory seems to have issues with disk sizes.
It's quite random, happens on both physical and virtual servers, local or SAN disks ...

I join you some screenshots.


Files

no_disk_size.png (98 KB) no_disk_size.png Olivier Mauras, 2013-11-27 13:59

Related issues

Related to Rudder - Bug #5542: FusionInventory: Doesn't display (most) disk sizes - branch 2.6Released2014-09-17Jonathan CLARKEActions
#1

Updated by François ARMAND over 6 years ago

I see two vector that can lead to that:

- Fusion does not know the size, and so Rudder can not know it
- Fusion report contains the data, but Rudder don't get it.

In the first case, we will work with Fusion Inventory to try to identify the problem and how to address them so that you get the relevant information.
For the second option, well, Fusion report are not very well normalized about what is a mandatory data for what kind of entries, and it may happen (read: it happened A LOT in the past) that for different storage system, different XML attributes are used for the size information.

So, before going farther... Could you please see in a Fusion XML report for a node that leads to missing data if the size information is prensent for the storage ? The best could be (if not private) to copy the relevant part of XML inventory, so we can analyze if the data is present, and if so, what is the problem with Rudder.

Thanks for the report!

#2

Updated by Vincent MEMBRÉ over 6 years ago

Some more informations from IRC:

12:05 < Vince_Mcbuche> coredumb: before 2.8, did you have disk size ? 
12:06 < Vince_Mcbuche> We haven't changed fusion inventory in 2.8
12:06 < Vince_Mcbuche> Are those nodes virtual machines ? 
12:15 < coredumb> Vince_Mcbuche: then i hadn't
12:15 < coredumb> Vince_Mcbuche: both virtual and physical
12:15 < coredumb> physical shows _some_ disk sizes
12:15 < coredumb> most not
12:16 < coredumb> didn't need it before so haven't checked much :D
12:16 < coredumb> Vince_Mcbuche: i know i see errors on 3TB drives when running fusion 
                  inventory
12:17 < coredumb> Q: "...-inventory --lo": Argument "3 TB" isn't numeric in 
                  multiplication (*) at 
/opt/rudder/share/fusioninventory/lib/FusionInventory/Agent/Task/Inventory/Input/Generic/Storages/HP.pm line 125, <$handle> line 13.

So it clearly comes from fusion inventory could not prcess the result of the function.

#3

Updated by Olivier Mauras over 6 years ago

Yes for this case, but on virtual machines, it just completes without error...

Here's the XML part on a VMware virtual machine:

    <STORAGES>
      <DESCRIPTION>SCSI</DESCRIPTION>
      <FIRMWARE>10 </FIRMWARE>
      <MANUFACTURER>VMware</MANUFACTURER>
      <MODEL>Virtualdisk    </MODEL>
      <NAME>sda</NAME>
      <SERIALNUMBER />  <TYPE>disk</TYPE>
    </STORAGES>
    <STORAGES>
      <DESCRIPTION>SCSI</DESCRIPTION>
      <FIRMWARE>10 </FIRMWARE>
      <MANUFACTURER>VMware</MANUFACTURER>
      <MODEL>Virtualdisk    </MODEL>
      <NAME>sdb</NAME>
      <SERIALNUMBER />  <TYPE>disk</TYPE>
    </STORAGES>

#4

Updated by François ARMAND over 6 years ago

  • Category set to 26
  • Status changed from New to 8
  • Assignee set to Vincent MEMBRÉ

OK, in the pasted inventory elements about storage, clearly the <DISKSIZE> element, which is the one used in Rudder to know the size, is missing and I don't see any other element that could have the size. So it is a missing part on Fusion Inventory - or several, like you already noted.

Sooo, let's discuss with the Fusion inventory community. Vincent, could you handle that, please?

#5

Updated by Olivier Mauras over 6 years ago

Any update ?

#6

Updated by Nicolas CHARLES almost 6 years ago

  • Assignee changed from Vincent MEMBRÉ to Nicolas CHARLES
  • Target version set to 2.10.6

related ticket on Fusion forge: http://forge.fusioninventory.org/issues/2718

#7

Updated by Nicolas CHARLES almost 6 years ago

  • Status changed from 8 to Pending technical review
  • Assignee changed from Nicolas CHARLES to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/482/files
#8

Updated by Nicolas CHARLES almost 6 years ago

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

Applied in changeset packages:commit:33a4125c32855bc520b42329c435e59c8941a21f.

#9

Updated by Jonathan CLARKE almost 6 years ago

Applied in changeset packages:commit:cb2d1e404980eb3803e6e9f178e7ee25d86782ea.

#10

Updated by Matthieu CERDA almost 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:

#11

Updated by Matthieu CERDA almost 6 years ago

This bug has been fixed in Rudder 2.10.6, which was released today.
Check out:

#12

Updated by Benoît PECCATTE over 5 years ago

  • Category changed from 26 to Web - Nodes & inventories

Also available in: Atom PDF