Rudder

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!

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.

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>

Any update ?

Applied in changeset packages:commit:cb2d1e404980eb3803e6e9f178e7ee25d86782ea.

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

• The release announcement: http://www.rudder-project.org/pipermail/rudder-announce/2014-October/000109.html
• The full ChangeLog: http://www.rudder-project.org/foswiki/bin/view/System/Documentation:ChangeLog210
• Download information: https://www.rudder-project.org/site/get-rudder/downloads/