ZeroDivisionError when there are no partitions of disk about ansible-cmdb

[fboender]

Hey Atoms,

Thanks for you bug report!

I can't seem to reproduce this problem. A size_available of 0 shouldn't be a problem with the latest version (v1.1 or master branch from Github), since the col_disk_usage is calculated as: (size_total - size_available) / size_total. I have several squashfs filesystems that have 0 available size.

Could you send me your entire out directory ([email protected]) or a reduced/redacted minimal sample that reproduces the error?

[Atoms]

ok, dig a little deeper, and yes, i was wrong :)

        {
            "device": "//x.x.x.x/isolib",
            "fstype": "cifs",
            "mount": "/var/run/sr-mount/6d6a0ce1-d0e7-54e1-d6ab-0549cc582508",
            "options": "rw,mand",
            "size_available": 0,
            "size_total": 0,
            "uuid": "NA"
        },

when i remove this from ansible_mounts then all goes well, i cannot see it in df output, so i think or this library is dead or just disconnected and left in xencenter....

so i think you need to check if size_total is not 0

[fboender]

The template was showing Disk Usage bars for disks smaller than 1MB, but they're supposed to be skipped just like the Disk Free and Disk Available columns. I've modified the template, and now the problem has gone away.

Thank you for your bugreport and help in reproducing the error. The master branch on github now includes a fix. I've released v1.2. You can download packages for v1.2 from https://github.com/fboender/ansible-cmdb/releases/tag/1.2

I'm closing this bug.