Debian 7 : The reported error was: float() argument must be a string or a number about ansible-cmdb

[fboender]

Hey Romain!

Thanks for the bug report. It's weird, cause I can't reproduce it with Debian v7.9. I'm running Ansible 2.0.0.2, so it could be that the problem is somewhere in between v2.0 and v2.1.

Can you paste the ""ansible_memory_mb" section from the offending host (looks like it's test.server.com)? That's where the problem should be located.

[romainrbr]

 "ansible_memory_mb": {
      "nocache": {
        "free": null,
        "used": null
      }

Running ansible-cmdb on OSX with the same Json file doesn't trigger any error.

[fboender]

Hm, that is very strange. It should look like this:

"nocache": { "used": 41, "free": 961 }

[romainrbr]

The host on which I ran ansible -m setup is an OpenVZ VM, which is why there is no cache value.

cat /proc/meminfo | grep Buffers
Buffers:               0 kB

[fboender]

Ah, that makes sense! Is there a valid "real" action with proper numbers, or is that also unavailable?

[fboender]

Sorry, I meant "section" instead of "action"

[romainrbr]

I don't think so.

Would it be possible to set the value to 0 if it's returned as "null" ?

[fboender]

I've just pushed a fix that returns "n/a" for that column in the host overview. It should be able to handle those hosts now. I'ts not a great fix, but the best I can do right now.

[romainrbr]

Thanks a lot!

[fboender]

You're welcome! Thanks for reporting the bug!

[fboender]

Oh, if the swap column is also not available, you may also get an error on that. I would be helpful if I had the whole output of ansible setup, so I can check everything. Could you send that to my email address ([email protected]), or is it too sensitive?